Technologies for generating and displaying virtual and interactive egifts

ABSTRACT

Technologies for unwrappable virtual egifts enabling recipients to redeem gift credits using payment accounts. In some examples, a system identifies a merchant associated with a giver, the giver being associated with a giver payment account and a recipient being associated with a recipient payment account. The system associates a policy with the gift credit and generates an image underlay identifying the gift credit and an image overlay hiding the image underlay and gift credit, the image overlay including a separable flap having a portion that appears unadhered to the image underlay, the separable flap being configured to trigger, in response to an input, an animated unwrapping effect that removes the image overlay to reveal the image underlay and gift credit. The system presents the image overlay and, in response to receiving the input, generates the animated unwrapping effect to remove the image overlay and reveal the image underlay.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application is a continuation-in-part of U.S. patent application Ser. No. 15/882,597, filed Jan. 29, 2018, which is a continuation-in-part of U.S. patent application Ser. No. 14/335,358, filed Jul. 18, 2014, now U.S. Pat. No. 9,881,299, issued Jan. 30, 2018, which is a continuation of U.S. patent application Ser. No. 14/219,276, filed Mar. 19, 2014, now abandoned, which is a continuation-in-part application claiming priority to U.S. Non-Provisional application Ser. No. 14/193,068, filed Feb. 28, 2014, now U.S. Pat. No. 8,751,392, issued Jun. 10, 2014, which is a continuation of U.S. Non-Provisional application Ser. No. 12/075,655, filed Mar. 13, 2008, now U.S. Pat. No. 8,676,704, issued Mar. 18, 2014. The contents of each of these applications are explicitly incorporated herein by reference in their entireties.

The present application is a continuation-in-part of U.S. patent application Ser. No. 15/882,597, filed Jan. 29, 2018, which is a continuation-in-part of U.S. patent application Ser. No. 14/335,358, filed Jul. 18, 2014, now U.S. Pat. No. 9,881,299, issued Jan. 30, 2018, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 12/475,122, filed May 29, 2009, now abandoned, which claims priority to U.S. Provisional Application No. 61/057,106, filed May 29, 2008. The contents of each of these applications are explicitly incorporated herein by reference in their entireties.

The present application is a continuation-in-part of U.S. patent application Ser. No. 15/882,597, filed Jan. 29, 2018, which is a continuation-in-part of U.S. patent application Ser. No. 14/335,358, filed Jul. 18, 2014, now U.S. Pat. No. 9,881,299, issued Jan. 30, 2018, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 13/301,327, filed Nov. 21, 2011, now abandoned, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 12/967,253, filed Dec. 14, 2010, now U.S. Pat. No. 8,285,643, issued Oct. 9, 2012. The contents of each of these applications are explicitly incorporated herein by reference in their entireties.

The present application is a continuation-in-part of U.S. patent application Ser. No. 15/882,597, filed Jan. 29, 2018, which is a continuation-in-part of U.S. patent application Ser. No. 14/335,358, filed Jul. 18, 2014, now U.S. Pat. No. 9,881,299, issued Jan. 30, 2018, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 13/754,401, filed Jan. 30, 2013, now abandoned, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 13/175,234, filed Jul. 1, 2011, now abandoned, which is a continuation of U.S. Non-Provisional application Ser. No. 12/967,253, filed Dec. 14, 2010, now U.S. Pat. No. 8,285,643, issued Oct. 9, 2012. The contents of each of these applications are explicitly incorporated herein by reference in their entireties.

The present application is a continuation-in-part of U.S. patent application Ser. No. 15/882,597, filed Jan. 29, 2018, which is a continuation-in-part of U.S. patent application Ser. No. 14/335,358, filed Jul. 18, 2014, now U.S. Pat. No. 9,881,299, issued Jan. 30, 2018, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 13/771,791, filed Feb. 20, 2013, now abandoned, which is a continuation-in-part of U.S. Non-Provisional application Ser. No. 13/686,189, filed Nov. 27, 2012, now abandoned, which is a continuation of U.S. Non-Provisional application Ser. No. 13/470,969, filed May 14, 2012, now abandoned, which is a continuation of U.S. Non-Provisional application Ser. No. 12/967,253, filed Dec. 14, 2010, now U.S. Pat. No. 8,285,643, issued Oct. 9, 2012. The contents of each of these applications are explicitly incorporated herein by reference in their entireties.

BACKGROUND 1. Technical Field

The present disclosure relates to digital egifts redeemable without use of a physical gift card, gift certificate, or electronic gift code but rather via the use of a gift card recipients' existing payment account(s).

2. Introduction

Gift cards allow individuals to give money to recipients. Recipients can use the gift cards as credit at a merchant. For example, a merchant website can be configured to allow a giver to purchase gift cards for the merchant. Example gift cards include personalized physical gift cards that a giver can print and/or mail to a recipient. Some merchants may provide email gift cards in which the giver enters an amount, quantity and recipient email address with a message. The redemption process is only through that merchant or its affiliate(s), and the website deducts purchases from the gift card balance. The merchant may apply any unused balance in the recipient's gift card account when redeemed. Typically, merchants expressly state that such gift cards cannot be reloaded, resold, transferred for value, redeemed for cash, or applied to any other account. Even email gift cards from merchants require various steps to redeem the gift cards. The merchant sends the recipient an email that provides a link to a principal gift card. In some cases, the merchant sends a long gift code to the recipient that can be input in a gift code field when making a purchase. These codes can be difficult to enter accurately because they are long and alphanumeric. Other problems can arise when using a link or code or requiring the user to perform additional steps to redeem the gift card.

A vendor can also offer gift cards from other merchants or resellers. Physical gift cards from a vendor can be mailed to the recipient. Gift cards can also be printed for similar use. However, a number of problems exist with these approaches. For example, consider a case where a user receives a $50 physical gift card for a restaurant but only spends $40 at the restaurant. No easy mechanism exists for the recipient to know how much money remains on the gift card. This leads to loss in funds on the gift card. Indeed, throughout the country, millions of dollars from gift cards are lost due to excess funds remaining unused. Such excess funds are often unused because the recipient forgets the gift card, fails to keep track of the funds, or throws the gift card away.

A New York Times article entitled “The More Convenient Gift Card”, found at http://bucks.blogs.nytimes.com/2010/11/19/the-more-convenient-gift-card/, found that various solutions have been proposed for making “gift cards easier and more convenient to use”, including a smartphone-based alternative to manage gift cards. However, the smartphone solution requires recipients to upload their gift cards and enter their gift card numbers so retailers can scan the gift card bar codes when shown on the smartphone. Despite efforts to improve gift card technologies, users still struggle managing their gift cards, often losing track of their gift cards and. The New York Times article ends with the question “How do you make gift cards more convenient, so you don't forget to use them or lose track of them?” Unfortunately, current solutions are not user friendly but rather complicated and limited, generally lacking adequate means for managing gift cards, tracking funds, and providing a realistic virtual egift experience for users.

SUMMARY

Additional features and advantages of the disclosure will be set forth in the description that follows, and in part will be obvious from the description, or can be learned by practice of the herein disclosed principles. The features and advantages of the disclosure can be realized and obtained by means of the instruments and combinations particularly pointed out in the appended claims. These and other features of the disclosure will become more fully apparent from the following description and appended claims, or can be learned by the practice of the principles set forth herein.

The present disclosure sets forth solutions to the aforementioned problems, among others, including the problems identified in the New York Times article explaining the challenges with users forgetting to use their gift cards and losing track of their gift cards and gift card balance. The present disclosure also sets forth solutions for generating virtual egifts that provide a realistic virtual experience for uses. Such virtual egifts can be used according to the approaches described herein.

In some examples, the approaches herein provide solutions for managing virtual egifts electronically so recipients can use their existing payment accounts (e.g., the users' bank accounts, credit or debit cards or accounts, etc.) to redeem a gift (i.e., credit associated with a virtual egift). When a giver creates a virtual egift instead of a gift card, the recipient can have an existing open-loop credit or debit card account. The pre-existing account is the users' normal open-loop credit or debit card accounts, which are available to the users when the virtual egift is created. No recipient account needs to be created specifically for the virtual egift. In some cases, if the recipient has an existing payment account registered with the virtual egift system/provider or a partner organization such as a financial institution, the virtual egift funds can be applied to the existing payment account and used via the existing payment account. If the recipient does not have an existing payment account registered with the virtual egift system/provider or a partner organization, the recipient may register their existing payment account(s) (e.g., the user's bank account, credit/debit card(s), etc.) with the virtual egift system/provider or a partner organization for use with the virtual egift. Having the recipient's payment account (e.g., bank account, credit card, debit card, etc.) registered can allow the system to track any transactions associated with the virtual egift and issue credit as necessary.

Any unused funds on a virtual egift can be cancelled, transferred/returned to the giver's or purchaser's account according to a policy defined by the giver for each virtual egift, or transferred to the recipient account according to a policy defined by the giver for each virtual egift. The policy can be implemented centrally at a server or distributed amongst entities (e.g., banks) to monitor the recipient's purchasing activity and apply virtual egift funds according to the policy when a triggering transaction occurs or a qualifying transaction is identified in a payment history of the recipient. Applying the virtual egift amount, depending on the types of accounts involved, can include reserving an amount of available credit, reserving an amount of money in an account, transferring money from one account to a holding account, transferring money to one or more merchant accounts directly, handling a transaction immediately such as is done with a debit card, handling a transfer of money in a batch mode for a period of time after a qualifying transaction, and so forth. Any combination of these and other transactional components can be applied to carry out the policy for any specific virtual egift.

The present disclosure also addresses various kinds of hurdles between a giver of a gift card and the recipient being able to redeem its value. Furthermore, the concepts herein address the issue of unused gift card funds being forgotten or lost (such as when a physical gift card is lost) and thus never redeemed. The approaches herein can involve enabling a giver of a virtual egift to identify a recipient of the virtual egift. A giver account and a recipient account (such as a credit/debit card account) are also identified. The recipient account is pre-existing in the sense that it is an account open and available for use by the recipient when the giver creates the virtual egift. Such a recipient account is typically an open-loop account meaning that it can be used generally and is not restricted to a merchant. A policy can be established to manage the transfer of money from the giver account to one or more merchants and/or the recipient account. The recipient account can be a payment account, such as a credit/debit card account, that existed and/or available to the recipient prior to the creation of the virtual egift.

Recipients can redeem their virtual egift in whole or part through a purchasing transaction (i.e., using their credit/debit card) in the same manner as they normally would make a purchase. If a transaction matches the policy (i.e., a purchase at a specified merchant, a dinner at a restaurant followed by a movie within x hours), then the virtual egift amount is applied to the transaction. The purchasing transaction occurs after the virtual egift is created. In other words, the virtual egift is not simply a transfer of money from one account to another. Any remaining amount on the virtual egift that is not applied to the transaction can be returned to the buyer, maintained in the recipient's account, or canceled according to the policy.

For example, a giver, George, goes online to give a virtual egift to a recipient, Rachel. George identifies Rachel as the recipient, enters $50 as the virtual egift amount, and associates the virtual egift with Merchant A. The system withdraws $50 from George's account, places a hold on $50 in George's account, transfers $50 from George's account to a third-party account, or otherwise sets aside or reserves those funds or available credit for use with the virtual egift. Then the system associates a policy with the virtual egift funds restricting application of the virtual egift money to purchases using the recipient's existing credit/debit card at Merchant A. Then, when Rachel uses her credit/debit card at Merchant A in accordance with the policy, the system applies the $50 to Rachel's purchase. Rachel does not have to present or enter any gift card code or use a physical gift card. This eliminates the hassles present for the recipient of a gift card. In one aspect, the gift can be deemed a “virtual egift” because no physical “card” exists.

In another sense, for the particular transaction, the recipient credit/debit card temporarily serves as a gift card containing funds associated with the virtual egift. The policy can be as simple as transitioning the money from the giver account to the recipient account. The policy can guide a control engine to hold, transfer, and/or manage the transfer of money from the giver account to the recipient account according to the type of account, i.e., credit or debit card. Because credit card accounts operate different from debit card accounts, the policy can achieve the same result of the recipient having a transparent experience of redeeming the virtual egift using an existing credit/debit card. The system manages the transfer of money according to the types of giver account and recipient accounts (e.g., credit or debit) so the process is seamless to the giver and recipient.

The approaches herein address these issues and enable the giver of the virtual egift to accurately identify the recipient such that the recipient payment mode (e.g., a credit card account, debit card account, PayPal account, etc.) can be retrieved. While various examples herein are discussed in terms of associating a virtual egift with a credit card, the same principles can be applied to any other payment mechanisms. Such payment mechanisms can include credit or debit cards, electronic payments (like PayPal or Google Checkout), merchant accounts, cash transactions, club or other loyalty cards, etc. As used herein, a reference to a credit/debit card is meant to cover all payment systems disclosed herein. Appropriate processing differences can be applied. Thus, applying a virtual egift amount from a giver to a recipient can occur in any variation between the disclosed accounts and differ accordingly, but with the same transparent result to the giver and recipient. One way to carry out the policy is to monitor the recipient purchasing transactions on a credit/debit card statement after a purchase. Qualifying transactions can be detected and thus trigger the application of the policy for applying the virtual egift.

An environment, such as a merchant website, is one example environment in which account information for givers and recipients can be obtained. Such environments can include a database of accounts that store credit or virtual egift, PayPal, or other payment related information. For example, a server can provide an interface in which a giver logged into a merchant website account can identify a recipient based on an email address, name, username or other personally identifying information. If such recipient has an account with the merchant website, the system and/or a merchant system can obtain credit and debit card information via a secured communication. Many merchant accounts, in order to facilitate one-click purchasing, store credit/debit card information. In this scenario, once the giver is identified, the giver's credit/debit card is already identified. As the giver identifies the recipient, the recipient credit/debit card account can be identified, thus enabling the remaining process of providing a “virtual egift” according to a policy as disclosed herein that eliminates the hurdles described above.

In some aspects, the approaches herein can implement the virtual egift concepts via a graphical, virtual egift configured to provide a realistic gift gifting, unwrapping, and use experience. To illustrate, an example method aspect of this disclosure can include receiving an identification of a merchant selected by a giver, where the giver of a virtual egift is associated with a giver payment account (e.g., credit or debit card), and a recipient of the virtual egift is associated with a recipient payment account (e.g., credit or debit card). The method can further include associating a policy with the virtual egift. The policy can be at least in part defined by the identification of the merchant.

The method can also involve generating an image underlay identifying the virtual egift and an image overlay which hides the image underlay and the gift credit identified in the image underlay. The image overlay includes a separable flap having at least a portion that appears as being unadhered to the image underlay, the separable flap being configured to trigger, in response to an input associated with the separable flap, an animated unwrapping effect that removes the image overlay to reveal the image underlay identifying the virtual egift. Moreover, the image underlay and/or the image overlay can include a single image, a plurality of images (e.g., a plurality of still and/or animated/moving images) such as a mosaic of images, a plurality of video frames/images (e.g., a video or animation), or any combination thereof.

The method can then involve presenting the image overlay hiding the image underlay, as well as other information such as the merchant, the giver, instructions, notes, balance checking links, etc.

In response to receiving the input associated with the separable flap on the image overlay, the method can involve generating the animated unwrapping effect to remove the image overlay and reveal the image underlay, and presenting the image underlay and the virtual egift, as well as any other information in the image underlay, such as the merchant, the giver, instructions, notes, conditions, etc.

An example method aspect of this disclosure includes receiving an identification of a giver of a virtual egift and a recipient of the virtual egift. A system practicing the method identifies an account associated with the giver and an account and/or a card-issuing bank associated with the recipient. Once the giver submits or confirms an order for such a virtual egift, the recipient can redeem the virtual egift through using the recipient account (i.e., using their existing credit/debit card). The process is independent of any physical gift card, gift code, bar code, and/or communication to the recipient. In other words, the recipient may not have a physical gift card, an access code, or a printable coupon. Rather, the recipient only needs to use a credit/debit card to make a purchase of the scope identified by the giver. In one example, the giver identifies $50 to be used at Restaurant A. The giver can provide a virtual egift including an overlay and underlay image, as previously described, which is configured to perform an animated unwrapping effect that resembles unwrapping a gift, when the recipient provides input, such as selecting a separable flap in the image overlay, to trigger the animated unwrapping effect. In some configurations, the giver can provide an optional notification to the recipient that the virtual egift has been ordered. A policy associated with the virtual egift is triggered when the condition (a purchase at Restaurant A using the credit/debit card) is met.

One trigger can launch or activate other triggers. An acquiring bank that manages communications between the merchant bank and the recipient's card issuing bank can implement all or part of the policy. For debit accounts, the debit issuing bank can implement the policy, or one or more other entities can implement the policy elsewhere. The recipient only needs to use a credit/debit card at Restaurant A and the system applies the virtual egift amount to be credited towards the transaction. The recipient does not have to do anything different: the recipient just shops using his or her existing purchasing mechanism. An intelligent network engine monitors transactions, receives triggering data, and transfers money or manages the credit/debit of the accounts according to the policy for each virtual egift. Once the basic function to process virtual egift in this manner is established, various policies can be applied in many different contexts to simplify transactions between individuals. These various policies cover different configurations and implementations disclosed herein. This scenario provides a better result and experience which eliminates the hurdles, hassles, and problems of gift codes and separate physical gift cards or printable coupons.

BRIEF DESCRIPTION OF THE DRAWINGS

In order to describe the manner in which the above-recited and other advantages and features of the disclosure can be obtained, a more particular description of the principles briefly described above will be rendered by reference to specific embodiments thereof that are illustrated in the appended drawings. Understanding that these drawings depict only exemplary embodiments of the disclosure and are not therefore to be considered to be limiting of its scope, the principles herein are described and explained with additional specificity and detail through the use of the accompanying drawings in which:

FIG. 1 illustrates an example computing system according to some aspects;

FIG. 2A illustrates an example flow for processing a virtual egift;

FIG. 2B illustrates an example debit card processing architecture;

FIG. 2C illustrates an example credit card processing architecture;

FIG. 3 illustrates an example method for processing a virtual egift;

FIG. 4A illustrates a sample system configuration for processing virtual egift;

FIG. 4B illustrates an example system configuration for processing virtual egift exclusively in an online retail environment;

FIG. 4C illustrates an example packet structure for communicating virtual egift transactions with a server;

FIG. 5A illustrates an example login prompt in a process for sending a virtual egift;

FIG. 5B illustrates an example virtual egift configuration screen in a process for sending a virtual egift;

FIG. 5C illustrates an example notification email to a recipient of a virtual egift;

FIG. 5D illustrates an example confirmation email to a recipient of a virtual egift that the virtual egift was successfully applied to a transaction;

FIG. 5E illustrates an example reminder email to a recipient of an outstanding balance on a virtual egift;

FIG. 6 illustrates an example flow for a releasing funds of a virtual egift;

FIG. 7 illustrates an example management portal for received virtual egift;

FIG. 8 illustrates an example management portal for sent virtual egift;

FIG. 9 illustrates an example interface for managing policies associated with virtual egift;

FIG. 10 illustrates an example method for managing virtual egifts;

FIG. 11A illustrates a first example user interface for adding promotions to a virtual egift;

FIG. 11B illustrates a second example user interface for adding promotions to a virtual egift;

FIG. 12 illustrates an example method for adding a promotion to a virtual egift;

FIG. 13 illustrates an example suggested recipient list of virtual egifts in a social networking context;

FIG. 14 illustrates an example virtual egift scheduler interface;

FIG. 15A illustrates an example interface for a group virtual egift;

FIG. 15B illustrates an example architecture for interfacing between online merchants, social networks, and banks;

FIG. 16 illustrates an example method for a group virtual egift;

FIG. 17A illustrates an example virtual egift interface integrated at a main level of an online merchant;

FIG. 17B illustrates an example virtual egift interface integrated at a general category level of an online merchant;

FIG. 17C illustrates an example virtual egift interface integrated at a specific category level of an online merchant;

FIG. 17D illustrates an example virtual egift interface integrated at an item level of an online merchant;

FIG. 18 illustrates an example method for intelligently populating and transitioning between what to offer a potential giver as they navigate an online merchant site;

FIG. 19 illustrates an example system for providing a predictive list of virtual egifts and/or recipients;

FIG. 20 illustrates a view of the example website with the predictive virtual egift widget expanded;

FIG. 21 illustrates an example method for providing a predictive list of virtual egifts and/or recipients;

FIG. 22 illustrates an example system configuration for processing a virtual egift in connection with a club card;

FIG. 23 illustrates an example method for processing a virtual egift in connection with a club card;

FIG. 24 illustrates an example user interface for dynamic suggestions for and adjustments to a virtual egift by the giver;

FIG. 25A illustrates a example user interface for a virtual egift for an item of an as yet unknown value;

FIG. 25B illustrates an example confirmation user interface for a virtual egift for an item of an as yet unknown value;

FIG. 26 illustrates an example system and control flow for processing virtual egifts for items with an as yet unknown value;

FIG. 27 illustrates an example method for processing virtual egifts for items with a value not yet known;

FIG. 28 illustrates an example payment processing chain;

FIG. 29A illustrates a layered view of an example configuration of a virtual egift according to some aspects;

FIG. 29B illustrates an example view of a virtual egift prior to an unwrapping event;

FIG. 29C illustrates a sequence diagram of an example unwrapping event;

FIG. 29D illustrates an unwrapped view of a virtual egift after an unwrapping event;

FIG. 29E illustrates a modified view of a virtual egift during and after an unwrapping of the virtual egift;

FIG. 30 illustrates an example configuration of a virtual egift and example views of the virtual egift;

FIG. 31 illustrates another example configuration of a virtual egift;

FIG. 32 illustrates another example configuration of a virtual egift including a wrapped view of the virtual egift and an unwrapped view of the virtual egift;

FIG. 33 illustrates an example method for generating and using a virtual egift;

FIG. 34 illustrates an example user interface for requesting a reverse virtual egift; and

FIG. 35 illustrates an example method of managing a group payment transaction.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below. While specific implementations are discussed, it should be understood that this is done for illustration purposes only. A person skilled in the relevant art will recognize that other components and configurations may be used without parting from the spirit and scope of the disclosure. Any particular function disclosed in connection with one embodiment or aspect can expressly be integrated into another disclosed embodiment, function or aspect. This disclosure considers mixing and matching of the various functions although particular functions are not specifically discussed in one example.

The present disclosure addresses the need in the art for removing hurdles in giving, redeeming, and processing gift cards, including virtual egifts created and redeemed without a physical gift card or code, and providing a realistic digital experience to virtual egift recipients. A brief description of a computing system or device in FIG. 1, which can be employed to practice the concepts herein, is first disclosed. A more detailed description of the various credit/debit processing infrastructures, example methods, and other processing infrastructure and concepts in conjunction with virtual egifts redeemable using an existing payment mechanism transparently (e.g., without any additional physical gift card, gift certificate or gift code) will then follow.

A recipient of a virtual egift can simply purchase a qualifying good or service with her Visa card, for example, and the payment processing infrastructure associated with the Visa card applies the virtual egift amount automatically to the transaction. This disclosure involves more than just a direct transfer of money from one person to another, or from a gift card to a credit card account, but rather involves a virtual egift approach in which a virtual egift is established at a first time having a policy, and a recipient, at a second time that is later than the first time, executes a purchasing transaction according to the policy. When that transaction is detected, the system will implement the policy and apply the virtual egift funds at a third time which is later than the first time, and can be approximately around the second time or later than the second time. The implementation and use of such a policy to guide/manage virtual egift payment through a recipient's use of an existing account introduces many features disclosed herein.

The virtual egift can include a gift credit for one or more merchants specified by a giver to a recipient. The virtual egift can be generated with an image underlay identifying the gift credit and an image overlay which hides the image underlay and the gift credit identified in the image underlay. The image overlay includes a separable flap or tab having at least a portion that appears as being unadhered to the image underlay and is configured to trigger, in response to an input associated with the separable flap or tab, an animated unwrapping effect that removes the image overlay to reveal the image underlay identifying the gift credit. Thus, when a recipient views a displayed image overlay of the virtual egift and interacts with the separable flap or tab (e.g., via a selection, a gesture, a voice command, a hovering activity, etc.), the animated unwrapping effect can be triggered to remove the image overlay in an animated fashion which resembles an unwrapping of a physical gift or a peeling of a physical label/sticker, and reveal the image underlay including an indication of the gift credit as well as other information such as the one or more merchants associated with the gift credit, a condition, a policy, instructions, notes, etc. The recipient can thus experience a gift unwrapping effect graphically, to expose the image underlay containing the gift credit and any other relevant information. The recipient can use the gift credit in the virtual egift as further explained throughout this disclosure.

The policy can include a class of goods or services, an amount of money, a merchant or group of merchants, a ceiling amount of money to be used in the virtual egift, a time frame for use of the virtual egift, one or more recipient accounts that when used can trigger the transfer of money from the giver account to the one or more recipient accounts, a predetermined period of time in which the amount of money associated with the virtual egift is to be used according to the policy, a remainder amount of money transferred from the giver account to the recipient account, etc.

This approach thus renders a recipient open-loop credit/debit card account into a hybrid open-loop/closed-loop account. The system monitors the activity of the account such that for an average purchase, the account is open-loop and not restricted, but the application of the virtual egift to specific purchases according the policy is considered closed loop.

For the sake of clarity, the methods herein are discussed in terms of an example computing system 100, as shown in FIG. 1, configured to practice the methods. The steps of each method outlined herein are exemplary and can be implemented in any combination and/or permutation thereof, including combinations that exclude, add, or modify certain steps. These and other variations are discussed herein as the various embodiments are set forth. The disclosure now turns to FIG. 1.

With reference to FIG. 1, an exemplary system 100 includes a general-purpose computing device 100, including a processing unit (CPU or processor) 120 and a system bus 110 that couples various system components including the system memory 130 such as read only memory (ROM) 140 and random access memory (RAM) 150 to the processor 120. The system 100 can include a cache of high-speed memory connected directly with, in close proximity to, or integrated as part of the processor 120. The system 100 copies data from the memory 130 and/or the storage device 160 to the cache for quick access by the processor 120. In this way, the cache provides a performance boost that avoids processor 120 delays while waiting for data. These and other modules can control or be configured to control the processor 120 to perform various actions. Other system memory 130 may be available for use as well. The memory 130 can include multiple different types of memory with different performance characteristics. It can be appreciated that the disclosure may operate on a computing device 100 with more than one processor 120 or on a group or cluster of computing devices networked together to provide greater processing capability. The processor 120 can include any general purpose processor and a hardware module or software module, such as service 1 162, service 2 164, and service 3 166 stored in storage device 160, configured to control the processor 120 as well as a special-purpose processor where software instructions are incorporated into the actual processor design. The processor 120 may essentially be a self-contained computing system, containing multiple cores or processors, a connection (e.g., bus), memory controller, cache, etc. A multi-core processor may be symmetric or asymmetric.

The system connection 110 may be any of several types of bus structures including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. A basic input/output (BIOS) stored in ROM 140 or the like, may provide the basic routine that helps to transfer information between elements within the computing device 100, such as during start-up. The computing device 100 further includes storage devices 160 such as a hard disk drive, a magnetic disk drive, an optical disk drive, tape drive or the like. The storage device 160 can include software services 162, 164, 166 for controlling the processor 120. Other hardware or software services are contemplated. The storage device 160 is connected to the system connection 110 by a drive interface. The drives and the associated computer readable storage media provide nonvolatile storage of computer readable instructions, data structures, program modules and other data for the computing device 100. In one aspect, a hardware module that performs a particular function includes the software component stored in a non-transitory computer-readable medium in connection with the necessary hardware components, such as the processor 120, connection 110, display 170, and so forth, to carry out the function. The basic components are known to those of skill in the art and appropriate variations are contemplated depending on the type of device, such as whether the device 100 is a small, handheld computing device, a desktop computer, or a computer server.

Although the exemplary embodiment described herein employs hard disk 160, those skilled in the art should appreciate that other types of computer readable media which can store data that are accessible by a computer, such as magnetic cassettes, flash memory cards, digital versatile disks, cartridges, random access memories (RAMs) 150, read only memory (ROM) 140, a cable or wireless signal containing a bit stream and the like, may also be used in the exemplary operating environment. Non-transitory computer-readable storage media expressly exclude media such as energy, carrier signals, electromagnetic waves, and signals per se.

To enable user interaction with the computing device 100, an input device 190 represents any number of input mechanisms, such as a microphone for speech, a touch-sensitive screen for gesture or graphical input, keyboard, mouse, motion input, speech and so forth. An output device 170 can also be one or more of a number of output mechanisms known to those of skill in the art. In some instances, multimodal systems enable a user to provide multiple types of input to communicate with the computing device 100. The communications interface 180 generally governs and manages the user input and system output. There is no restriction on operating on any particular hardware arrangement and therefore the basic features here may easily be substituted for improved hardware or firmware arrangements as they are developed.

For clarity of explanation, the illustrative system embodiment is presented as including individual functional blocks including functional blocks labeled as a “processor” or processor 120. The functions these blocks represent may be provided through the use of either shared or dedicated hardware, including, but not limited to, hardware capable of executing software and hardware, such as a processor 120, that is purpose-built to operate as an equivalent to software executing on a general purpose processor. For example, the functions of one or more processors presented in FIG. 1 may be provided by a single shared processor or multiple processors. (Use of the term “processor” should not be construed to refer exclusively to hardware capable of executing software.) Illustrative embodiments may include microprocessor and/or digital signal processor (DSP) hardware, read-only memory (ROM) 140 for storing software performing the operations discussed below, and random access memory (RAM) 150 for storing results. Very large scale integration (VLSI) hardware embodiments, as well as custom VLSI circuitry in combination with a general-purpose DSP circuit, may also be provided.

The logical operations of the various embodiments are implemented as: (1) a sequence of computer-implemented steps, operations, or procedures running on a programmable circuit within a general use computer, (2) a sequence of computer-implemented steps, operations, or procedures running on a specific-use programmable circuit; and/or (3) interconnected machine modules or program engines within the programmable circuits. The system 100 shown in FIG. 1 can practice all or part of the recited methods, can be a part of the recited systems, and/or can operate according to instructions in the recited non-transitory computer-readable storage media. Such logical operations can be implemented as modules configured to control the processor 120 to perform particular functions according to the programming of the module. For example, FIG. 1 illustrates three services Service 1 162, Service 2 164 and Service 3 166 which are services configured to control the processor 120. These services may be stored on the storage device 160 and loaded into RAM 150 or memory 130 at runtime or may be stored as would be known in the art in other computer-readable memory locations.

The term “system” or similar terms also apply to the herein disclosed systems for processing various types of transactions. There are differences in systems for processing credit card and debit card transactions. It is assumed that with the policies and processing disclosed herein, that appropriate adaptations are made for specific systems where necessary. Those of skill in the art will understand the hardware components used for accomplishing such transactions.

The physical systems performing the functions disclosed herein can be found in any geographic location. For example, one or more of the banks, servers, and physical infrastructure performing the steps herein may be outside the United States. Therefore, all processes should be interpreted as also including the concept of a recipient performing a purchase in the United States, communications leaving the United States (confirmation, authorization, instructions, etc.) for a foreign entity, and communications being received from the foreign entity that achieves the results discussed herein.

Virtual eGIFTS

FIG. 2 illustrates an example flow 200 of an example approach for processing a virtual egift. The examples disclosed herein are discussed in terms of example system 100 or computing device as shown in FIG. 1 configured to practice the various steps, operations, tasks, etc. A more specific example system for implementing this flow 200 is illustrated in more detail in FIG. 4 with respect to a control engine that manages the redemption and processing of each virtual egift according to its policy via communications and instructions with various accounts and/or merchants accounts. Feature 202 represents a giver interface. An example will be used to step through the various blocks. Assume that a giver desires to give a $50 virtual egift to a recipient. The interface 202 enables the giver to either input identification information and recipient account information or have it prepopulated based on a previous login. The interface 202 can be a web interface, a software client interface, a point of sale interface that a store employee uses on behalf of a giver, a self-service kiosk, a voice-based interface, an interface via a handheld device, a multimodal interface, speech interface, or any other suitable interface. The system 100 identifies, via the giver selection, a predictive approach, or some other approach, a recipient(s) such as a mother, sister, or friend of the giver, etc., and an amount that the giver desires to give to the recipient. The recipient credit/debit card data/account is identified via a secure communication to a database or inserted by the giver or recipient if necessary or possible. Through one or more different methods, the giver account and recipient account are identified.

It should be noted that the giver does not have to know the recipient's payment account information (e.g., the recipient's credit or debit card number, the recipient's bank account number, etc.). Instead, the giver can identify the recipient or provide information the system can use to identify the recipient. If the recipient has an existing payment account registered with the virtual egift system/provider or a partner organization such as a financial institution, the virtual egift funds can be applied to the existing payment account and used via the existing payment account. The system can identify the payment account registered for the recipient without the giver knowing or providing the payment account number or other sensitive payment account information. If the recipient does not have an existing payment account registered with the virtual egift system/provider or a partner organization, the recipient may register their existing payment account(s) (e.g., the user's bank account, credit/debit card(s), etc.) with the virtual egift system/provider or a partner organization for use with the virtual egift. In some cases, the recipient can be prompted to register a payment account if one is not already registered or identified by the system. For example, the recipient can receive an alert or notification indicating that the recipient has received a virtual egift. The recipient can then register a payment account, such as a debit/credit card account or a Paypal account, with the virtual egift system/provider or a partner organization. Having the recipient's payment account (e.g., bank account, credit card, debit card, etc.) registered can allow the system to track any transactions associated with the virtual egift and issue credit as necessary.

In some cases, the virtual egift system can provide group offerings. For example, a user or entity (e.g., a business or organization) can purchase a batch of virtual egifts for multiple users (e.g., employees, customers, vendors, family members, friends, colleagues, etc.). If the actual recipients are known at the time of purchase, the virtual egifts can be created for the identified recipients and the egift funds applied to existing payment accounts registered by the identified recipients. If the identified recipients do not have registered payment accounts, the identified recipients can register one or more respective payment accounts with the virtual egift system/provider or a partner organization as previously explained. In some cases, a user or entity can purchase the batch of virtual egifts without the actual recipient known at the time the virtual egift is purchased/created. In other words, the user or entity can purchase and create a batch of virtual egifts for multiple users without identifying the multiple users. For example, the giver (e.g., the purchasing user or entity) can purchase a batch of virtual egifts for unspecified recipients and receive respective links or codes corresponding to virtual egifts created for the unspecified recipients. Each recipient can receive a respective link or code associated with a respective virtual egift, which the recipient can use or redeem with one or more merchants, promotions, trade shows, or in any other manner as described herein.

The virtual egift system can also provide other group offerings. For example, the virtual egift system can provide many-to-one egift options were multiple givers can purchase a combined egift amount for a recipient, as further described below. Moreover, in some cases, a giver can create a virtual egift tied to multiple merchants, as further described herein. For example, the virtual egift can be configured with a policy that allows use of the virtual egift with multiple merchants. The recipient of the virtual egift can thus apply funds associated with the virtual egift for transactions with one or more of the multiple merchants.

The timing of the creation and redemption of the virtual egift is relevant. In one example, the creation of the virtual egift by the giver occurs at a first time, say Monday morning at 9:00 AM. The policy is established at that time or perhaps relatively close to that time, such as the virtual egift is good for purchases at restaurants. The recipient then will at a second time, which is later than the first time, execute a purchasing transaction at a restaurant, say Friday night at 6:00 PM. The policy can then be implemented (money transferred, paid, etc.) at the time of the transaction around Friday at 6:00 PM, or the system may scan the recipient transaction history say every Saturday to determine whether qualifying transactions exist. Assuming that the system can identify restaurant transactions on the recipient transaction history, it would then detect the Friday night restaurant purchase and implement the policy for that purchase.

The recipient bank might desire such scanning of the recipient purchasing history to remain anonymous. In this case, a secure communication between a central control entity and the recipient account holder can provide higher level policy data. For example, a participating recipient bank can have a module to perform such scanning and receive data from a central control entity to monitor Rachel's account for purchases at the Olive Garden and notify us of the purchase. Rachel's bank or credit card issuing entity can monitor her account and provide the data of the transaction at the level needed. For example, the control entity can instruct the bank that the virtual egift is for $40 at Olive Garden and to monitor for 6 months and report back (1) whether a purchase was made at Olive Garden, and if it was under $40, then the amount, or if it was over $40. Assume one month later Rachel makes a $42 purchase at Olive Garden. Her bank can notify the control entity that a purchase was made for over $40 dollars (thus maintaining the secrecy of the total amount). The control entity can then apply the policy for the entire virtual egift. If Rachel spent $35, her bank can report the purchase and the amount as $35. The policy then causes $35 of the virtual egift to be applied to the transaction and maintains the record that $5 is still available. If after 6 months no other purchase is made by Rachel, the control entity can simply transfer the rest of the funds to Rachel's account or take some other action based on the policy. Since Rachel's bank was instructed to monitor her accounts for virtual egift-related activity for six months, once the six month expires, that monitoring simply expires as well. This approach can simplify and separate the implementation of the policy from a control entity and a giver or recipient bank.

The interface can have access to the giver and recipient accounts such that the giver does not have to enter credit/debit card or checking account information. Either way, the interaction can confirm to the giver that a sufficient level of information exists to carry out the virtual egift transaction. This can include that an authorization communication has confirmed that the recipient has a valid credit/debit card. The specific recipient card to be used to redeem the virtual egift can be provided, optionally without the card number, to the giver. The interface can optionally tell the giver that the recipient Visa credit card is to be used for the virtual egift or can enable the giver to select which payment mode the recipient should use, i.e., the system may instruct the giver that the recipient's Visa Credit card and MasterCard Debit card are both available, and to choose which one is to be used. The giver can click a “give” button that begins the transaction. Upon triggering the transaction, information is transmitted to block 204 that will withdraw, hold the amount ($50), or reserve in a line of credit from a giver account and associate it with the recipient credit/debit card account and the policy for managing the virtual egift. The particular process of retrieving the virtual egift amount from the giver account will depend on the type of account is used or other policy considerations. Applying the virtual egift amount, depending on the types of accounts involved, may include processes as reserving an amount of available credit, reserving an amount of money in an account, transferring money from one account to a holding account, transferring money to a merchant account directly, handling a transaction immediately such as is done with a debit card, handling a transfer of money in a batch mode a period of time after a qualifying transaction, and so forth. Any combination of these and other transactional components can be applied to carry out the policy for any specific virtual egift.

If the recipient has an existing payment account registered with the virtual egift system/provider or a partner organization such as a financial institution, the virtual egift funds can simply be applied to the existing payment account and used via the existing payment account. If the recipient does not have an existing payment account registered with the virtual egift system/provider or a partner organization, the recipient may register their existing payment account(s) with the virtual egift system/provider or a partner organization for use with the virtual egift, as previously explained.

If the recipient does not have an account, the system can either send a notification to a recipient indicating that someone wants to give them a virtual egift and encouraging the recipient to set up an account. If the recipient does not have an account because the recipient is a child, for example, who is not old enough to have a credit/debit card, the system can suggest to the giver a suitable proxy recipient who has an account, such as a parent or guardian. If the recipient is unable or unwilling to set up an account and no suitable proxy recipient is available or known, the system can take some default action. The default action can include mailing a check or a traditional physical gift card to the recipient.

The information received from block 202 is sufficient to identify a giver account from which to draw or hold the $50 for the recipient. Also, the information from block 202 can identify a recipient account such as a bank account, credit/debit account, merchant credit card, online payment account, or other device or mechanism associated with purchases and/or payments so the recipient can receive the money. As noted above, the terms “credit card” and “debit card” encompass credit cards and debit cards as well as PayPal, cash, club cards, checks, merchant-specific credit cards, and other payment modes. Accordingly, in block 204 the system identifies and associates the various accounts with the virtual egift in preparation for completing the transaction. Optional block 206 involves sending a notice to the recipient. Because no physical gift card is given, if the giver wants to give a virtual egift of $50 to the recipient for use at a restaurant, the system can provide an email or other notification via text or voicemail or other mechanism. One example notification states “George has given you a $50 virtual egift to Olive Garden, please use your Visa and $50 will be applied to your purchase at Olive Garden.” No interaction is necessary with a notification. Indeed, no notification is required for the transaction. The recipient may only know about the virtual egift after it is redeemed, or when the giver or system informs the recipient. The merchant can also inform the recipient when the virtual egift is redeemed. Redemption of the virtual egift is independent of any communication to the recipient or any notification although other features, upselling, or optional variations to the policy of the virtual egift can be applied through notifications and interactions between the giver and/or seller.

A policy associated with the virtual egift can be as simple as applying the virtual egift amount to the transaction by the recipient at any merchant(s). Other policies and variations are further disclosed. Several other aspects are associated with the optional notification 206 to the recipient. As has been noted, the notification is optional inasmuch as the information associated with the giver and the recipient is already obtained and can be processed without any automatic or other notification at all. The giver can simply call up the recipient and tell the recipient that the recipient got a $50 virtual egift for use at Olive Garden and all the recipient needs to do is use their credit card or any of the designated payment modes or accounts. As noted above, the giver interface can notify the giver that the card is redeemable through the recipient's credit card. The policy can cover several accounts and a multitude of scenarios. The virtual egift is redeemable through using the recipient's credit/debit card at the merchant as though they were making a normal payment without the existence of the virtual egift. The policy is implemented through control mechanisms on a server, distributed at various banks, or associated with the various banks involved to monitor the recipient purchasing activity to identify a triggering transaction to implement the policy of the virtual egift. For example, the recipient credit card account can have a monitoring module associated with it when a virtual egift is redeemable with that account. The monitoring module can identify when a purchase is made and notify a central control entity, which can cause the system to apply the virtual egift funds according to the policy.

In another aspect, however, given the framework disclosed herein, email or other electronic notification to the recipient can provide other features. The email can be a simple notification such that the recipient does not have to interact with the email at all in order to use the virtual egift. The notification can have no mechanism (or no mandatory mechanism) for feedback, reply, or confirmation. In other aspects, communication or interaction with the recipient can be desirable for security or other purposes. For example, the email can provide some information such as “George has given you a $50 virtual egift to Olive Garden. Do you know George and do you want to accept this virtual egift?” The system can require the recipient to click a confirmation button link or perform some other interaction to confirm that the recipient desires to use the virtual egift. Interactions with the notification can modify or confirm the policy. The recipient may receive a communication that says, “George has given you a virtual egift for $50, do you want to redeem it through your Visa credit card (and add $5) or through your debit card (and add $3).” Based on the selection of the recipient, the policy is established and accessory features are added, if any. These interactions are optional and, even when present, the interactions, communications, and notifications with the recipient are not required for redemption of the virtual egift.

As a value-added service, the system can, as part of the interaction, allow the recipient to reserve a table at Olive Garden, invite others to join, show a custom menu including updated prices for items based on the virtual egift amount (which would be free for items under $50), a meal planner application to see an estimated total cost (after the $50 virtual egift) of a specific set of items (such as an appetizer, two entrees, drinks, dessert, etc.), and the like. The interactions can include verification questions to further confirm that the recipient is the appropriate person and that they know the giver, and so forth. Those of skill in the art can understand various mechanisms for confirming and authorizing the transfer of funds from the giver to the recipient.

In yet another aspect, the notification 206 can include options presented to the recipient for how the virtual egift will be managed. The notification to the recipient can state, “George has provided you with a $50 virtual egift to any restaurant of your choice. If desirable, please select from the following options.” In this example, the giver did not specify a particular restaurant but provided that the virtual egift was for the recipient to go to dinner. Thus, the card was provided for a class of goods or services (food). The notification is a opportunity for specific restaurants (as members of the class) to seek additional business. The notification can include an option selectable by the giver or the recipient, e.g.: for Olive Garden, Red Lobster, or P.F. Chang's. Additionally, communication with the various databases associated with these restaurants can include additional information such as P.F. Chang's offers an additional $5 if the virtual egift is used at P.F. Chang's. This provides an upselling opportunity available to the merchants. The method can include receiving information associated with a giver giving a virtual egift for a class of items such as restaurants, or hardware stores, or grocery stores, etc. Data is then retrieved for the specific species of that class and potential offers that can be associated with each of those species.

Thus, a database is accessible while processing the virtual egift, in which offers from Olive Garden, P.F. Chang's and Red Lobster are determined to be available. Options can be presented to the giver for selection to upsell or cause them to want to add the offers to the base virtual egift. These offers are combined with the notification that is sent to the recipient, if any optional notification is sent. The system presents a communication to the recipient and receives a selection of one of the species. Assume that the recipient sees an offer for the Olive Garden in which an additional $5 is added to the virtual egift amount. The system then handles the entire transaction such that when the recipient uses their credit/debit card at the Olive Garden. The $50 is applied to the transaction as well as an additional $5 from the Olive Garden. This $5 can be a coupon discount or an additional transfer of money to the recipient's account from the Olive Garden or some other entity during or following the transaction. The policy can manage the final transaction with all the various participants, giver, recipient, merchant, and others.

The system can present an option in the communication where the recipient does not select any of the species of the class but merely desires to receive the virtual egift for use at any restaurant. In such a case, the recipient receives the notification they received a virtual egift for a restaurant but selects no specific restaurant. The next time the recipient goes to any restaurant and uses an appropriate payment mechanism according to the policy for the virtual egift, the system (such as an acquiring bank or other node or control engine in the system) applies the virtual egift for $50 to that transaction and the species options which were presented in the communication are cancelled at that stage and no longer viable.

Where a genus (such as restaurants) are applied in the policy, and where the system scans the recipient transaction history to determine whether a triggering transaction exists, there may be some ambiguity in the recipient payment history regarding whether a purchase was at a restaurant. In such a case, the system may initiate a confirming interaction via a communication with the recipient to confirm that the purchase last night at 6 PM at “Mama Lucia's” was a restaurant. If that is confirmed by the recipient, then the system implements the virtual egift policy for that transaction.

In one aspect, the virtual egift is associated with a group of payment mechanisms for a single giver and/or recipient or multiple givers and/or recipients. For example, the virtual egift can be tied to a VISA debit card and an American Express credit card. A transaction at the restaurant using either can trigger the application of funds associated with virtual egift to the recipient account, the merchant account or in any other fashion. In another aspect, the virtual egift is tied to a checking account shared by a recipient pair. A transaction at a restaurant made via either spouse's check card or a physical check can trigger the virtual egift. The giver can specify a recipient routing number, such as the routing number printed on the bottom of a physical check, so that the system can apply the virtual egift to the recipient's checking account. A debit card used on that checking account can also trigger the virtual egift transaction. In each case, the virtual egift can have a policy associated with its redemption that the system monitors recipient purchasing transactions and follows with respect to transferring funds.

When the system receives information associated with the giver and the recipient, the species options that are presented in the above scenario can also be geographically selected. The location of the recipient is known based on information in the database, a mobile device location, a recent purchase, and/or other sources, and the system can identify and present an initial set of specific businesses to the recipient. This option can also be dynamic. A recipient living in Virginia can be notified of receipt a virtual egift for any of a series of species restaurants that are within 10 miles of their home. If the recipient travels to Italy, and use of their credit card or other location-based mechanism indicates that they are now in Rome, a follow up email can be provided with a new set of offers associated with restaurants within the vicinity of where the credit card is actually being used. In this scenario, the earlier offer can be cancelled, modified, or maintained. In any event it is preferable that once in Italy, if the restaurant in Italy provides an additional upsell offer for use in association with the virtual egift, then once that payment mechanism is used according to the new offer, all offers are then cancelled and considered fulfilled. The merchants can attach additional limitations to their upsell offers as well, such as “minimum $25 purchase”, “valid until November 31^(st)”, “for use at the Baltimore location” or “valid Wednesdays only”. These variations represent different features illustrating how the policy can manage any given virtual egift. As can be appreciated, the variety of policies that can be applied to a virtual egift to manage how its payment is triggered is endless and all such variations are considered within the scope of this disclosure. Policies can mix timing, geography, classes/species of goods and services, individuals, groups of purchases (i.e., a series of items purchased that are related or associated according to the policy) and so forth.

Location-based data can also trigger an offer to a giver. Assume a recipient, Rachel, who previously received a virtual egift for the Olive Garden from a giver George, is again at the Olive Garden. Rachel's location as identified by her mobile phone, either automatically or manually such as based on a check-in to FourSquare, can trigger a notice to George that states, “Rachel is at the Olive Garden. Do you want to treat her to dinner?” A preauthorized offer already associates the giver account to the recipient account. If George says “Yes” or otherwise confirms the notice, the system can trigger the transaction. A communication to Rachel of any type, including a connected telephone call, can notify Rachel that George is treating her to dinner and to use her Visa card in the normal fashion. However, no communication is necessary.

The system can notify the merchant from which the recipient is making the purchase, such as Red Lobster. Location-based services can identify that the recipient of a Red Lobster virtual egift is at a Red Lobster location. The notification can inform the wait staff at Red Lobster that it is the recipient's birthday and request that they sing “Happy Birthday” to the recipient. Alternatively, the notification to the merchant can provide some information regarding recipient preferences for food, products, or service, such as “the recipient prefers Diet Coke with no ice”. Then the wait staff can act on the notification information to provide customized service to the recipient in such a way that the experience is a pleasant surprise to the recipient. In this manner, the merchant can know of people who are at their location and have virtual egifts. Such data can provide the merchant with a mechanism to identify the recipient, such as a photo because the recipient has yet to use their credit/debit card for the purchase. In this scenario, a location-based service can identify that the particular person is at the merchant because of their handheld device, and a communication with a control engine managing the virtual egifts can identify that a virtual egift for the merchant is available for that user. The merchant can receive a photo ID of that patron even before they would pay for their goods/services to provide the enhanced level of service based on the information they receive.

Next, block 208 indicates that the recipient makes a qualifying transaction. An example of a qualifying transaction is the recipient using their credit/debit card to purchase dinner at the Olive Garden. The simplicity of this approach is that there is no code, separate physical gift card, or any other step that needs to be taken in order for the recipient to enjoy the benefits of the $50 gift. The recipient simply needs to make the purchase in the normal manner in which they would purchase such an item. The new result of the concepts disclosed herein is a simplification of the giving and redemption of virtual egifts such that no money is ever lost or failed to be redeemed due to policies that can manage the process of handling any remainder funds such that they are never lost.

Block 210 indicates applying at least part of the amount to the transaction. Assume that the virtual egift amount was $50 and the transaction was $40. The system applies $40 of the $50 to the dinner at Olive Garden. The system can hold the $10 for future purchases at the Olive Garden or handle the $10 in various other approaches according to the policy for the virtual egift as described further below. The recipient can establish, via policies, a preference to use only a portion of the virtual egift amount for a first transaction and reserve the remaining portion of the virtual egift amount for a second transaction at a later time.

The system can apply at least part of the amount to the transaction in a variety of ways. FIG. 2B illustrates an exemplary debit card processing architecture 214. For example, assume the recipient 216 uses a debit card 218 for the qualifying transaction. In the debit card processing infrastructure 214, the recipient 216 presents the debit card 218 to a merchant 220 at a point of sale. The merchant 220 or recipient 216 swipes the debit card 218 through a scanner or otherwise obtains the debit card number, such as by entering the number into a computing device. The merchant system contacts the financial institution 224 indicated by the debit card number, either directly or through a debit card processing center 222. The financial institution 224 verifies that funds are available in the recipient account 226 and approves the transaction by immediately (or nearly immediately) withdrawing funds from the recipient account 226 and transferring the funds to the merchant 220. In this debit card processing infrastructure 214, if the debit card account only has $20 in the account (and the purchase was for $40), then the policy/control entity 228 can dictate to apply at least part of the virtual egift amount to the transaction. The system identifies that the recipient wants to use the debit card for a $40 transaction, whereas they only have $20 in their account, the system can credit $20 to the recipient account 226 from the giver account 230 prior to completing the transaction, at which point the debit card can be used to complete the transaction. If the recipient account 226 has sufficient funds, then the system can process the qualifying transaction in a normal fashion, and then credit the recipient account 226 the appropriate amount of $40 from the giver account 230 after the transaction with the merchant is completed.

In another aspect, a system directly pays the merchant 220 associated with the qualifying transaction at least a portion of the amount from the giver account 230 based on the transaction. For example, once the recipient uses their debit card 218 in the qualifying transaction, a separate transaction occurs in which the system pays $40 to the merchant from the giver account 230 at the time of the transaction and the $40 does not pass through the particular debit card account of the recipient. Other acquiring banks or intermediate accounts can be used to hold money and process it either immediately or in batch modes at a later time. The particular processing can depend on the characteristics (credit/debit/other) of the giver account, recipient account, merchant account, acquiring bank account, etc.

Additionally, the recipient can choose to apply the entire virtual egift amount, part of the virtual egift or none of the virtual egift in a purchase transaction. In this way, the recipient can control spending by choosing to pay from their own pocket for a purchase now and save their gift for later, when perhaps a particular item is on sale or when the recipient knows they will need additional funds, such as from a virtual egift to make purchases. For example, a recipient can inform a merchant to not apply a particular gift at the time of purchase since the recipient knows that on Black Friday the Dremel Multimax power tool at Home Depot will be half off. The recipient knows that Black Friday is a big spending day and that she typically overspends that day. She can choose to redeem her virtual egift on Black Friday to help control her spending.

FIG. 2C illustrates an exemplary credit card processing infrastructure 232 in which the system can credit the recipient account at the time of sale or shortly thereafter. In a credit card processing infrastructure 232, the issuer 236 of the credit card 217 lends money to the recipient 216 to be paid to a merchant 220. In most cases, the merchant 220 and/or the recipient 216 swipes the credit card 217 through a machine known as reader. If the card issuer 236 approves the transaction, an acquiring bank 238, which receives credit card transactions from the merchant 220, then credits the merchant's account 242. A credit card association (not shown) may also be involved to set the terms of transactions for merchants, card-issuing banks and acquiring banks. The merchant 220 can pay the acquiring bank 238 a fee for processing the transaction. Once approved, the card issuer 236 posts the transaction to the recipient's account 226. At the end of the billing period, the cardholder 216 receives a credit card statement from the issuer 236, at which time payment for the transaction is due. In this credit card processing infrastructure 232, the system can credit the recipient account 226 when a bill is due, such as a monthly credit card bill, shortly before or on the due date. In this way, the system can hold on to the money, potentially earning interest on the money until the last minute it is needed to satisfy the virtual egift transaction. This floating period can be one source of revenue to fund the virtual egift system infrastructure and/or to provide a profit to the operators of the virtual egift system infrastructure. Also shown in FIG. 2C is a policy/control entity 228 and the giver account 230 which are used to communicate with, monitor and manage the virtual egift transactions according the principles and concepts disclosed herein.

If the system 214, 232 processes virtual egifts in a batch or delayed mode, it can on a periodic (daily, weekly, monthly, etc) or triggered basis (upon a large transaction, or two weeks after the creation of the virtual egift, or one week after a known birthday, etc.) review the transaction statement of the recipient to scan for qualifying transactions. For example, if a recipient makes a purchase at the Olive Garden, the structure and data in the credit/debit card statement is known. The system can scan the statements for Olive Garden transactions, identify dates, locations amounts and/or any other relevant data that is needed for a particular policy, and then apply the policy accordingly to transfer money from the giver account to the recipient account. Again, the variations between giver and recipient accounts being debit, credit accounts or other types of accounts can be considered such that the system achieves the transfer of money or available credit or other compensation to the recipient.

The system 214, 232 can process credit cards and apply virtual egifts in real time (or substantially real time) or in batches. A merchant that processes credit cards typically has a merchant account for receiving credit card payments. If the merchant accepts many credit card payments, the merchant can process credit cards in batches rather than one at a time. In a batch-based approach, the merchant accepts payment via credit card from a customer and submits the payment to the merchant account. Then the acquiring bank, or an organization that accepts payment on behalf of the merchant, checks the customer's name and credit card number for authenticity. The acquiring bank can also check the transaction and the amount with the bank that issued the credit card. The acquiring bank holds onto the payment while validation takes place. If all checks are valid, the system generates an approval code and the merchant keeps that code together with information relating to the sale. The merchant can store authorized cards in batches and send the batch to the acquiring bank each day at close of business and/or at some other interval. The acquiring bank can send the batch to a credit card association (not shown) that debits the customer's accounts and credits the appropriate account. Once the acquiring bank receives payment from the credit card issuer, the acquiring bank pays the merchant, optionally minus a processing fee. Although batch processing can be convenient for a merchant, there are times when he or she may not benefit from it. The same or similar principles can be applied to process virtual egifts in batches. The virtual egift processing system can be a separate entity that intercepts the flow of the authorization process, or can be integrated as part of any or all of the acquiring bank, card issuer, merchant point of sale, giver/recipient accounts, credit card association control, and so on. In one example, as a virtual egift is established, a code or a module is established to monitor the recipient purchasing activity using the recipient credit/debit account(s) 226. When a triggering transaction occurs (purchase at a restaurant, particular merchant, or a series of purchases occur), the system can notify the policy/control entity 228 and then receive further instructions on how to consummate the transaction for the virtual egift and handle any further processes such as remainder amounts of money on the virtual egift, and so forth. All variations on actual implementation are included within the scope of this disclosure with respect to locations within the system where certain processes take place.

In all of these scenarios, the management of the transaction and transfer of funds are transparent to the giver and the recipient in that the system conducts the actual purchasing in the same way the recipient would purchase the product or service with the debit or credit card and without a separate gift card, code, or certificate. Just as credit card companies receive a small percentage of each transaction, the virtual egift system disclosed herein can also deduct a small percentage of each virtual egift transaction, share it with the credit card, or debit card system. The virtual egift managing entity 228 can obtain payment for use of the virtual egifts in a variety of ways.

Feature 212 of FIG. 2A is an optional feature that represents a notification to the giver and/or the recipient after the transaction. One example of this step includes providing information on a physical receipt associated with the qualifying transaction, stating something like “Happy Birthday Mom. I hope you enjoyed your dinner.” The notification acts as a reminder that the giver provided the virtual egift for that particular transaction. Email notifications can also be provided to the giver, recipient, and/or a third party. After the giver gives the virtual egift, the giver may desire to receive a notification when the recipient redeems the. After the giver sends the virtual egift, the giver can receive an email that identifies that the recipient used the virtual egift for dinner on a certain date. Any timing mechanism can be applied. Furthermore, the system can send an email or other communication to the recipient after the qualifying transaction that can provide a further personalized message from the giver such as “I hope that you enjoyed your dinner, thanks for all you do.” The after purchase notification can also include details about the policy for any remainder amount. The notice can state “I hope you enjoyed your Olive Garden virtual egift! You have $15 remaining on this virtual egift for your next Olive Garden purchase. After 6 months, if not used, the $15 will be transferred to your debit account automatically [or be cancelled, or be transferred to a third party, or any other option according to the policy].”

Third party notifications are not limited, however, to the merchant and the system can send a notification to any other person or entity. For instance, a brother who gives his sister a virtual egift for her birthday can instruct the system to notify her husband when she has redeemed it and what it was redeemed for so that the husband does not purchase the same or similar item for her birthday or so the husband can purchase a matching accessory.

The new process outlined in FIG. 2A provides an easier mechanism to transfer a virtual egift money amount from a giver account to a recipient account in a manner that is transparent to the recipient. This process can be managed by a specific policy such that even if the virtual egift amount or remainder is forgotten, it is never lost and always managed according to a policy. Reminders can be sent prior to the remainder amount being cancelled or transferred to an account. The virtual egift is redeemed through an existing payment mechanism for the recipient and requires no codes, physical gift cards or coupons, and includes policies, reminders or processes to assure no money is forgotten or lost.

Often recipients will have multiple virtual egifts with varying amounts that they lose track of or fail to redeem. These approaches provide a new result of reducing the barriers to obtaining a greater benefit from a virtual egift with far less effort on the part of the recipient and/or the giver.

FIG. 3 illustrates an example method for processing a virtual egift. The method may be practiced by an individual computing device or a computing device in communication with other computing devices within a network. One or more of the various computing devices can reside in a merchant bank, an acquiring bank, a giver account, a recipient account, a merchant, credit card association, a policy control entity or engine, and so forth. The system receives an identification of a giver of a virtual egift and a recipient of the virtual egift (302). The system identifies a giver account and a recipient account for managing the transfer of the amount of money from the giver account to the recipient account (304) or to a merchant bank according to a policy. The recipient account can already exist and can be an open-loop payment mechanism that is not restricted to a merchant or shopping portal, such as a credit/debit card or checking account. An optional notice is sent to the recipient associated with the transfer of the amount of money to the recipient (306). As shown above, the giver account and the recipient account each are an established account such as a Visa, MasterCard or American Express credit card and the like or a debit account. The information received in step 302 can further include a transaction processing policy such as how to handle the money amount if the recipient does not engage in a qualifying transaction within a period of time, and so forth. The policy can transfer unused funds in the virtual egift to the recipient credit/debit card account after x months or any timeframe. One alternative to the method described in FIG. 3 is for the system to invite a potential recipient to establish a recipient account if one does not exist. The system can send a message in any form (e.g., orally, text message, email, voicemail, etc.) inviting the potential recipient to set up an account. The message can explain that someone wishes to give a gift to the potential recipient but the potential recipient needs an account for the gift to occur. The giver remains anonymous or the giver may reveal himself in the request for account setup. The message may optionally include a link to a page requesting the potential recipient's name and credit card information so that the recipient's account can be established. This scenario is useful when helping the technologically challenged navigate through the account set-up process.

Another alternative to the method described in FIG. 3 is for the system to set up accounts through another person for children or those that do not have credit/debit cards. For example, a mother can setup a giver or recipient account for her teenage daughter who does not yet have a credit/debit card with the mother's card information. The mother can make redeeming purchases on behalf of her daughter. In this way, it is possible to establish user accounts for the technologically challenged or underage givers and recipients.

The system receives information that the recipient has made a qualifying transaction using their existing recipient account (308), the transaction occurring at a second time which is later than the first time. The system then applies at least part of the amount of money to the qualifying transaction (310) in a manner according to whether the transaction is a credit or debit transaction for both the giver and the recipient. The system can apply the amount of money to the purchase to yield a remaining amount of money. Upon the recipient using the recipient payment mode to make an additional purchase, the system can apply the remaining amount of money to the additional purchase in a manner associated with the recipient payment mode or transfer the remaining amount to the recipient. Alternatively, the system can apply the amount of money to a purchase by processing a purchase history associated with the payment mode to identify a previously made purchase, and applying the amount of money to the previously made purchase.

An optional feature is the system providing a notification to the giver and/or the recipient (312). In one aspect, a transaction can trigger the use of more than one virtual egift. For example, if the recipient purchases an item from Home Depot for $95 and has two virtual egifts to Home Depot, one for $20 and one for $40, then the system can apply all available virtual egifts up to the purchase price. The system can apply both virtual egifts for a total of $60 such that the recipient ends up paying $35 for the item.

The system can receive an identification of a giver of a virtual egift and a recipient of the virtual egift, and associate the giver with a giver account and the recipient with a recipient account. The system can associate a policy with the virtual egift and monitor transactions of the recipient using the recipient account. Then the system can receive information based on the monitoring that the recipient has made a transaction using the recipient account according to the policy, and apply an amount of money from the giver account for the transaction according to the policy.

The system can optionally receive a condition from the giver, and apply the amount of money to the purchase if the purchase satisfies the condition or according to a policy. The system can implement this optional step via one or more policy enforced at a merchant, acquiring bank, control engine, merchant bank, issuing bank, and/or other level in the virtual egift processing infrastructure. The condition that dictates the policy can restrict the virtual egift to a retailer, a group of retailers, a geographical region, a class of goods or services, an item, a time range, a date range, and/or a maximum per-transaction value. The system can apply virtual egifts based on policy limitations. For example, if a recipient has multiple virtual egifts to a same merchant, when the recipient makes a purchase at that merchant, the system can apply the virtual egift with the earliest expiration date. Alternatively, the system can credit the merchant at the time of the transaction, and then initiate a dialog with the recipient at a later time to determine which of the available virtual egifts to apply to the transaction. If the recipient does not indicate which virtual egift to apply, the system can apply a default virtual egift. Any entity within the virtual egift processing infrastructure can subtract a service fee (flat fee and/or a percent) from the amount of money associated with the virtual egift. The service fee can be a recurring fee, a one-time fee, a per-purchase fee, and so forth.

The system can optionally receive from the giver a request to establish a subscription, the request indicating at least one subscription requirement. Then the system can establish the subscription to automatically apply a subscription amount of money to transactions of the recipient or applies a gift amount according to a policy based on the at least one subscription requirement. The policy may involve just transferring money from a giver account to the recipient account. For example, the giver can set up at the beginning of every year a schedule of virtual egifts one week before the birthday of his or her family members and five best friends. The system can automatically carry out the notice and processing of the virtual egifts throughout the year. If a parent has a child at college, the virtual egift can be for any grocery store and a subscription causes $200 to be applied at the beginning of each month. This policy easily enables the recipient to simply use their virtual egift (credit/debit card) at a qualifying merchant (grocery store) and it is applied on schedule according to the subscription policy.

Givers and recipients can receive notifications associated with the virtual egift. For example, the system can notify the recipient of at least one of the amount of money, a condition associated with the amount of money, the payment mode, and the giver. The system can also notify the recipient that the amount of money was applied to the purchase, transmit a stored message to the recipient from the giver, and/or send a notification to the giver that the amount of money was applied. Notifications can include a description of an object of the purchase to which the amount of money was applied, a purchase time, a purchase date, and a merchant. The system can send notifications via email, SMS, instant message, tweet, social networking, automated voice call, physical mail, and/or any other suitable communication medium. The giver or recipient can interact with the notifications to be presented with options or information about the current policy for the virtual egift, and can interact with the notification to change the policy or modify how the virtual egift will be handled in the future. The recipient may want to regift the remainder amount to a third party and such option can be presented via a notification and then carried out under a new policy for the remainder virtual egift.

The system can provide for regifting of a virtual egift by receiving a request from the recipient to transfer at least part of the amount of money to a third party and/or another virtual egift still belonging to the recipient but having different policies. The transfer can be not as part of a purchase. Then the regifted virtual egift can then associate the at least part of the amount of money with a third party payment mode. Upon the third party using the third party payment mode, the system applies the at least part of the amount of money to the purchase in a manner associated with the third party payment mode. Part of the virtual egift may be managed by one policy and another part (the regifted part) by another policy.

Virtual egifts can include bonus offers from third parties. The system can receive a bonus from a third party and add the bonus to the amount of money. The bonus portion of the virtual egift can include its own policy or policies separate from other policies associated with the virtual egift amount, such that when the bonus policy is satisfied on top of the other virtual egift policies, the system applies both the virtual egift amount plus a bonus amount to a purchase. The system can also provide notification to the giver, recipient, and/or a third party associated with the bonus that the bonus was applied by transmitting a stored message to the recipient, for example, from the third party. Such a message can be something like “I added $20 to Dad's virtual egift for dinner, have a big dessert!” In this manner, the system presents to the bonus giver, if authorized, information about the recipient virtual egifts and the identity of the primary giver.

The recipient of the virtual egift can, in some circumstances, manage, change, or remove a policy associated with a virtual egift. The system can receive a request from the recipient to use the amount of money to make the purchase outside the purchase condition, deduct a penalty from the amount of money according to the purchase condition to yield a reduced amount of money, and apply the reduced amount of money to the purchase in a manner associated with the recipient payment mode. As can be appreciated, the processing system disclosed herein provides much greater flexibility and possibilities when processing virtual egifts.

eGIFT Processing Infrastructure

FIG. 4A illustrates an example block diagram 400 of a network 416 in which the system can operate. Network 416 includes various components that make the processing disclosed herein possible. A giver interface 402 is used in a variety of ways to receive initial information about the giver. For example, the giver interface 402 can simply be a web site accessible via a web browser in which there is an opportunity for the giver to provide the basic information to identify the recipient, the amount associated with the virtual egift and so forth. The giver interface 402 can be a device such as kiosk, ATM machine, or gas pump.

The giver interface can function in different ways as well. A giver can come to a kiosk or an ATM with a physical gift card to use at a company such as the Olive Garden. The giver wants to transfer those funds for use according to the methods disclosed herein, effectively converting a physical gift card to a virtual egift having a policy for its management. The giver can insert the physical gift card into a card reader of the kiosk that reads the amount left on the card, identifying information for the account and the restaurant such as Olive Garden. The giver can then insert their credit/debit card and the interface would therefore have the necessary information with respect to the giver (which in this case would be the actual physical gift card, a gift code, and/or a gift certificate as the “giver”, the recipient, the amount and the recipient account). Optionally, the giver only needs to identify the recipient such that the recipient account can receive the gift card amount. This interaction enables a same person to be both the giver and the recipient when they have a physical gift card. This process easily facilitates the transfer of those funds from a physical gift card into a virtual egift allowing usage of those funds via their standard credit/debit card. This provides a way for both givers and recipients to avoid the pitfalls associated with physical gift cards or with gifts requiring gift codes. This transaction, however, in one aspect, does not just transfer the money to the credit/debit card account. If the physical gift card is for the Olive Garden, the system retrieves that information from the gift card and applies it as a policy for the recipient. Therefore, the closed-loop nature of the physical gift card is carried over to the virtual egift such that it is redeemed only at the merchant. The other aspects of the policy can also be applied, such as after six months of non purchases at the designated merchant, then the money is transferred to the recipient account, or any other desired policy.

Similarly, a giver interface 402 can include a website in which a giver types into a web interface a particular gift code that may or may not be associated with a physical gift card. The system can receive this information to identify an amount, the giver, and the company to which the virtual egift applies. Then the giver can also add their information as the recipient and therefore provide the necessary information via the giver interface for the remaining transactions to occur under the processes defined herein. In this manner, any recipient of a physical gift card can easily transfer that gift card to the virtual egift system disclosed herein. The recipient no longer has to worry about losing the gift card or forgetting to use all the money on the gift card.

The disclosure temporarily turns to FIG. 4C, which illustrates an example packet 406 as is introduced in FIG. 4A. FIG. 4C shows packet 406 with various data fields. The exact names, types, sizes, and order of data fields in the packet are exemplary. The packet can be implemented in any variation thereof, including any combination or permutation of these and/or other data elements. These example fields include a security header 472, a general header 474, information about the giver 476, information about the recipient 478, a currency amount 480, a payment mode 482, a time associated with the virtual egift 484, a location or geographic limitation associated with the virtual egift 486 and another optional field 488 or fields. The amount can be in any currency: domestic, foreign or virtual. The system can automatically handle conversion between currencies, if needed. Some of the packet fields shown are optional. The use of such a packet enables a central control engine 404 to receive a single set of data associated with a virtual egift and carry out all of the transactions associated with monitoring recipient purchasing activities, apply egift money as guided by the policy, and credit or debit money from the appropriate accounts.

The packet structure can allow for the information about the giver 476 and the information about the recipient 478 to identify more than one individual. The packet can include information about each giver 476 and recipient 478 in the form of, for example, an email address, name, account number, or other unique identifier. Further, in the case of multiple givers, the amount field 480 can include one or more sub-amounts corresponding to each giver. The payment mode 482 can be identified by credit card number, bank account number, routing number, club or loyalty card number, PayPal address, and so forth. In one case, the payment mode can be a user profile such that any payment mode associated with that user profile is able to use the virtual egift.

As has been noted above, this packet, in one aspect, does not include any account information or credit card information for the giver or recipient. However, the packet does include a sufficient amount of giver and recipient information such that a control engine 404 can receive that data, and in a secure manner, identify the various accounts that are needed to transfer the money and manage the distribution of the virtual egift funds as instructed by the packet and/or a policy. The security information 472 can be used according to those of skill in the art to ensure that at the giver interface, a fraudulent giver cannot log into the system and thereby inappropriately gain access to giver, recipient, or third-party accounts. The packet can be transmitted to a secure environment that stores the account data and carries out the transaction.

Based at least in part on data received from the giver interface 402, the system can develop a packet 406 as discussed above and shown in FIG. 9. The packet 406 includes the information to manage, create, trigger, or perform other actions associated with the virtual egift and optionally the additional information. At a basic level, the packet 406 provides information about the giver, the recipient, the amount, and other management information about how the amount is to be applied. The packet can identify whether the giver account and recipient account are credit or debit accounts. The network 416 receives this packet at a control engine 404. This can represent a computing device, acquiring bank, debit card bank, issuing bank, and/or server within the network 416 that can manage the policy of distribution, use, and/or notifications associated with the virtual egift. The control engine 404 can be part of or in communication with an acquiring bank. Network 416 can be the Internet, an intranet, a virtual private network, an encrypted network, electronic or fiber-optic network, and/or any other kind of network that can include a wireline or wireless network. Therefore, the giver interface 402 can also be a wireless interface via a wireless device with the appropriate software to enable communication of such information.

The control engine 404 communicates with the giver account 408 and a recipient account 410 and optionally with a third party account 412 and/or a merchant or bank 414. The control engine 404 can communicate with or operate on any one or more of these systems. For example, the third-party account 412 does not necessarily need to be involved in each transaction. Furthermore, the control engine 404 can optionally communicate directly with the merchant or bank 414. Accordingly, when a giver gives a $50 virtual egift for the Olive Garden to the recipient, the control engine can utilize a default processing mechanism in which the giver account 408 is deducted by $50 and that money is held in a third-party account 412. In an alternate mechanism, the system deducts $50 from the giver account 408 and credits the recipient account 410 with the $50 directly but with no or some restrictions on that $50. One example of $50 being restricted or reserved is if the recipient account is a debit account and the giver has only $75 left in the debit account after the $50 is deposited. If the giver tries to make a $30 purchase, which would leave only $45 in the account, that transaction can be rejected inasmuch as that $50 is reserved and unavailable for use except according to the policy for managing the virtual egift. In either scenario, when the recipient makes a purchase of $50, for example, at Olive Garden 414, then those funds can be released from the recipient account according to the policy, can be successfully processed and the $50 can be paid to the merchant either directly or indirectly. In a direct scenario, the system transfers the $50 to Olive Garden's account. In one indirect scenario, the $50 is paid to Olive Garden directly from the recipient's account, and the system transfers the $50 to the recipient's account, thereby effectively reimbursing the recipient after the fact. Thus, the system handles the transfer of money according to the giver account (credit, debit, or other) and the recipient account (credit, debit, checking, cash, or other).

As has been noted above, the system can guide the flow of funds from the giver account 408 to one or more recipient account 410, the third-party account 412 and/or the merchant bank 414 in a number of ways. These varieties are disclosed above and not repeated here. In each case where egift funds are applied to a purchasing transaction, any of the various scenarios can be used to process the virtual egift. The egift funds can also be applied to non-purchase fund transfers. For example, if the recipient chooses to donate to a particular charity, the system can apply the egift funds, still according to any policies in place, even though the donation is not a “purchase” of a good or service.

FIG. 4B illustrates a second example block diagram 450 of an architecture 450 in which the system can operate. The architecture 450 represents a model operated by an online merchant such as Amazon.com. For purposes of illustration, Amazon is used herein to represent a generic online merchant in which the data about the giver and recipient are stored or received via a user interaction to process a virtual egiftas disclosed herein. A giver of an egiftcommunicates with the control engine 456 through a network 454 via a user interface 452. The user interface 452 can be a web browser on a desktop computer or mobile device, an application on a desktop computer or mobile device, a telephonic interface, a text-message based interface, a kiosk interface, and so forth. The actual interface details can be implemented in any of a number of different ways, as can be appreciated by one of skill in the art. The giver has an account 458 with Amazon and desires to give a virtual egift to a recipient having a recipient account 460 with Amazon. Each of the user accounts for the giver and the recipient with Amazon can be associated with underlying bank accounts, credit cards, and/or PayPal accounts, for example. In an environment like Amazon, or Visa, MasterCard, PayPal, or any other universe of users in which account information is available, the system disclosed herein can be used to easily identify givers, recipients and apply policies to exchange virtual egifts easily and seamlessly.

The giver provides instructions to the control engine 456 through the user interface 452 to send a virtual egiftto the recipient. The giver can provide partial information to the control engine 456 to identify the recipient, such as an email address, username or a first name, last name, and mailing address. The control engine 456 and the user interface 452 can provide the giver a way to select which types of information to provide. As the giver enters information, the control engine 456 and the user interface 452 can also provide feedback to the giver regarding the entered information. For example, if the giver enters a mailing address, the control engine 456 can look up the mailing address in the Amazon customer database and determine that three separate user accounts list the same mailing address. Thus, the control engine 456 can indicate to the giver that it needs additional information to disambiguate which of the three separate user accounts is desired and optionally prompt the giver to provide a specific type of information to disambiguate between the three separate user accounts. When the giver has entered sufficient information to identify the recipient, the control engine 456 can display, via the user interface 452, a confirmation of the identified recipient so that the giver is sure that the correct person has been identified. This confirmation can include any information, such as text, images, a purchase history, video, audio, personal metadata, a list of friends, and so forth, pulled from the recipient's Amazon account or other information available publicly or via other channels, such as a social network via an API call.

When the giver has identified a recipient with the control engine 456, the giver also indicates an amount of money to give as a virtual egift and, optionally, any restrictions, conditions, or limitations on the virtual egift. The amount can be fixed or dynamic. For example, as discussed above, the amount can be $50 to any item on Amazon.com. Alternatively, the amount can be a virtual egift including a restriction to a purchase of any HP inkjet printer from Amazon.com, up to a maximum of $200. The actual egift amount is not determined until the recipient makes a purchase of the indicated item.

Because the control engine 456 controls the egift implementation based on policies, handles the transactions, and controls (at least indirectly) giver and/or recipient payment accounts, the control engine 404 and merchant or bank 414 of FIG. 4A are effectively merged into one entity in FIG. 4B. As part of the process of creating a virtual egift, the control engine 456 can withdraw funds from the giver account 458 and place them in a third-party account 462 until the recipient redeems or uses the virtual egift. Alternatively, the control engine 456 places a hold on the egift amount in the giver account 458 until the virtual egiftis redeemed. The hold can be a reservation of available credit on the giver account, which is charged when the recipient redeems the virtual egift. The control engine 456 can implement other fund processing variations as well. In one aspect, the user accounts 458, 460 at Amazon are proxies for actual bank accounts such that Amazon can deposit, withdraw, hold, and perform other operations on funds in the actual bank accounts. The control engine 456 generates a virtual egift associated with the recipient account 460.

The control engine 456 can provide an optional notification to the recipient via email, the recipient's Amazon account, or some other medium. Then, the control engine 456 monitors each recipient purchase through Amazon.com to determine if the purchase matches the terms, if any, of the virtual egift. When the control engine 456 detects a qualifying purchase, the control engine 456 can apply the egift funds to the recipient account 460, keep the egift funds as payment for a product or service Amazon provides, or transfer the egift funds to one or more vendor 464 of the product or service purchased. The control engine 456 can redirect a payment to a vendor 464 for a purchase so that the purchase is made by the recipient as if the recipient pays with his own account 460 but the control engine 456 performs back-end manipulations to redirect the payment out of the giver account 458.

In one variation, the control engine 456 can update the interface for the recipient as the recipient browses the Amazon product catalog. For instance, if the virtual egift is $50 for any item on Amazon.com, the control engine 456 can automatically reduce the prices listed on the various product pages as the recipient browses Amazon.com to reflect what the price would be if the $50 virtual egift were applied. Therefore, the product page for a $120 boxed set of DVDs can show $70 instead of $120. If the virtual egift has conditions, restrictions, or limitations associated with it, the automatically updated prices can reflect that too. For example, if the virtual egift is $30 for a microwave oven, then the product page for the $120 boxed set of DVDs can still show $120, but a page for a GE countertop microwave oven is reduced by $30. Additionally, the control engine 456 can display automatically and/or manually generated promotions that are only redeemable when purchasing a product or service with all or part of a virtual egift. For example, Amazon may offer 10% off specific goods or services when purchasing with a virtual egift. A merchant may refund a certain money amount to Amazon when an item is purchased, thus awarding Amazon for directing sales to the merchant.

Virtual eGIFT User Interfaces

The disclosure now turns to some example user interfaces, as shown in FIGS. 5A-5E. FIG. 5A illustrates a basic log in screen 500 where the giver enters credentials before entering into a giver interface to begin a virtual egift transaction. This provides basic information such as giver or recipient name 502 and a password 504, but can incorporate other authentication techniques, such as speaker verification, biometric identification, swiping a credit card (or other identification card) through a card reader, personal confirmation such as recipient high school, pet name, and so forth. The authentication can be tied to a phone number or other unique, user-identifying information.

FIG. 5B assumes that the giver has logged in and the giver's name is “George”. Here, screen 506 illustrates a welcome screen for George, optionally including a greeting 508, and presents various specific options to George for giving a virtual egift. The system can pre-populate various fields and menus using stored information about the user, George. If such a recipient name is not pre-populated, then the interface receives information from George that is sufficient via the packet or other appropriate approach, for the control center to identify an account for the recipient. The recipient list can be prepopulated based on previous egifts or preentered names and information associated with various people that would receive a virtual egift from George. This can be presented in drop down menu 510 or via some other user interface component. George can identify recipients by name, address, email address, mobile phone number, bank routing number, credit card number, a gift-card specific account username, number, or address, any personal data from the recipient, and so forth. If the virtual egift management entity is called VirtualGiftCard, potential recipients can register with VirtualGiftCard and establish a VirtualGiftCard identity such as recipient @VirtualGiftCard, www.VirtualGiftCard.com/recipient, or #recipient. These unique identifiers through a virtual egift provider allow potential recipients a simple, easy to remember way to share their recipient identity with others for receiving virtual egift. For example, a person who desires to be a virtual egift recipient can register their identity on VirtualGiftCard and share that identity with their friends, family, workplace, schoolmates, and even post it on Facebook or some other public forum or social network in order to elicit or otherwise promote others to give the recipient virtual egifts. In an environment like Amazon.com, recipients can be identified based on existing user accounts very easily. Further, a person desiring to receive virtual egifts in this manner can create wish lists of desired items that the system shares with potential givers.

A recipient desiring to receive virtual egifts from a particular giver who does not have a user account can send a message via any communication medium such as email, text message, voicemail, etc. informing the giver that a virtual egift wish list exists for the recipient and encouraging the giver to establish a user account in order to give a virtual egift. This solution solves the problem of a giver asking a recipient what they want for a special occasion and the recipient replying “I don't know”. Once the recipient decides they would like to receive a virtual egift for particular goods or services, the recipient can send a message to the potential giver informing the potential giver that they have created a wish list for virtual egifts.

The interface 506 shown can be an application or website, for example. Alternatively, the interface can be a JavaScript or other widget that pops up on another page, such as a Facebook profile page. In the example of a Facebook profile page widget, the interface can be pre-populated with the information of a person currently displayed on the Facebook page.

In one example of this scenario, George does not need to know the credit card number of the recipient. This provides a level of security with this interface in which George only knows the name, address, and/or other identifying data of the recipient. If such information is provided in packet 406 shown in FIG. 4A to the control engine 404, a certain threshold of confidence can be associated with identifying a particular recipient. The system can give some confirmation information to George, such as the recipient's city of residence, car model, spouse name, high school, pet name, or other information by which George can uniquely identify the recipient, to ensure that George knows that the system has identified the right person. However, such various security measures can be taken in manners to those of skill in the art in order to appropriately identify the correct recipient in field 510 so that thereafter the appropriate recipient account 410 can be utilized to process the virtual egift.

Next, the giver fills in an amount field 512 or selects from a list of amounts from a drop down menu or other graphical or multimodal manner. The drop down menu can be prepopulated with a list of previous amounts given to this particular recipient, common amounts given, or suggested amounts based on the selected merchant, and so forth. The system can also analyze the recipient's purchase history and suggest an amount and/or a merchant. For example, if the recipient goes to a favorite restaurant every two weeks and spends an average of $65 per visit, the system can suggest a virtual egift to the favorite restaurant and base a suggested amount on the average, mean, mode, maximum or other suitable amount spent per visit.

Another field 514 provides a drop down menu (or other graphical or multimodal mechanism) of merchants, but other input forms can be used as well, such as predictive text entry, a web search, and so forth. Home Depot is shown but other merchants can certainly be used to fill in or prepopulate this menu. These can include merchants that have previously processed virtual egifts or that have been used by the recipient.

The giver can enter other conditions 516 associated with the virtual egift based on a variety of factors. For example, George desires to provide a timing element for the virtual egift. George can give the virtual egift to Rachel who is travelling to Italy for two weeks for her 10-year anniversary. As part of a gift, George wants to help support that vacation and limit the virtual egift's use to Rachel's purchases and costs incurred during that two weeks or related to that two weeks. For example, any purchase Rachel makes in Italy during those two weeks would qualify, but a purchase of swimming trunks 10 days before the trip can also qualify because it relates to the trip to Italy. Accordingly, George can attach other conditions, via a policy, in which a certain time frame and/or a geographic limitation is provided. Therefore, a variety of other conditions can be added to the virtual egift to limit its use appropriately. If the conditions include a two-week window at a certain amount of time as well as a geographic location, then the conditional use of those funds can be based not on a merchant but rather on purchases made using the credit/debit card while in Italy during a two week period of time. In this way, George can tailor the virtual egift more specifically. A control engine, acquiring bank, card issuing bank, or other entity can monitor recipient transactions and compare them against the policy for applying the egift funds. The recipient can also provide manual input to help implement an egift policy. If the virtual egift is not used in the time frame, the policy can indicate that it is cancelled and the funds released, no longer held, or transferred back to the giver.

FIG. 5C illustrates an example notification email 518 which explains to the recipient 520, Rachel, that says, “George has sent you a virtual egift for Home Depot for $75. You can use the virtual egift by simply using your Visa card at Home Depot or at homedepot.com”. The email can include a CC to the giver 522, in this case george@email.com. The notification is optional and can be provided via other communication modalities as well, such as voicemail, Facebook communication, tweet, SMS, personal call, a mailed letter or postcard, and so forth. The notification can include other instructions as well. For example, if Rachel is going on the 10-year anniversary trip mentioned above, then the message 524 can include, for example, “George has sent you a virtual egift for use on your 10-year Anniversary trip in Europe. The virtual egift is for $100 and will be credited or used for purchases made with your Visa during your two week trip only while you are in Italy. Enjoy your Anniversary!” In the case of purchases abroad, the virtual egift can be converted to the foreign currency all at once or at each individual transaction, or however the system determines is the best fit given the cost of exchanging currency. For instance, if the $100 virtual egift is applied to multiple transactions, each exchange of currency can incur a $4 service charge plus a percentage of the amount exchanged. The system can wait until the two week trip to Italy is over, then exchange, in a single transaction, as much as is needed for the multiple transactions the recipients made to avoid incurring the currency exchange service charge multiple times. Alternatively, if the foreign currency is prone to fluctuations, the system can incur the service charge on a per transaction basis to avoid losing value due to a fluctuating exchange rate. A giver can choose to give a virtual egift in a foreign currency if they know the recipient will be in a foreign country to avoid per transaction charges and additional service fees.

These notifications can include targeted advertisements. For example, the system can perform an analysis of the recipient's general purchasing history, virtual egift based purchasing history, available balance on the virtual egift, interactions with the giver, an online shopping history, a location history, and other personal factors to generate a recipient advertising profile. Based on the recipient advertising profile, advertisers can target individual recipients and classes of recipients with custom tailored advertisements. The recipient advertising profile for egift spending habits can be different than the recipient advertising profile for general spending habits. Thus, an advertiser can target the recipient based on the recipient's egift spending history in order to extend a more attractive offer, promotion, or advertisement to the recipient.

FIG. 5D illustrates an email 526 that the system can optionally send to Rachel after she makes a purchase using her credit/debit card. The message 528 can include several details. For example, the message 528 explains how much of the virtual egift has been applied to the purchase. Assume $29.64 has been applied to the transaction for a shovel purchased at Home Depot from a $75 virtual egift. The $29.64 is subtracted from the total $75 virtual egift amount to yield a balance of $45.36 remaining available for use at Home Depot or homedepot.com. The notice can provide this type of information as a reminder to use the remaining amount of the card or to provide the recipient with options to change the policy or apply part of the policy, such as reverting the remaining funds to go into their checking account. Optionally, the system adds a link to the communication so that Rachel can manage the virtual egift in a certain way. This also, as noted above, can include a CC to the giver of the virtual egift.

FIG. 5E illustrates an exemplary optional reminder communication 536 from the virtual egift services to the recipient, Rachel. This is one mechanism of managing the use of the egift funds such that the funds do not go “stale” or get lost and thus never redeemed. The system can schedule virtual egift reminders to send to Rachel if she does not use the funds within two months or six months or any appropriate selectable time frame. The system can configure the optional reminders and their schedule, but the giver and/or the recipient can also configure the reminders. In one example, the giver sets a reminder schedule and the recipient modifies the reminder schedule via a web, telephone, SMS, or other interface. The message 538 explains that the email is a reminder of a $45.36 available virtual egift balance for the Home Depot purchase. There is also a further note that after December 1, the amount will revert to general applicability for any transaction at any merchant using the recipient's credit/debit card. This again is another optional safety mechanism so that the funds are never “lost” or remain unused. If the recipient never goes to Home Depot, ultimately at some point the system can simply apply the egift funds to the recipient's first transaction that occurs after December 1. Other alternates exist in which the money can simply be credited to their account with a notice that George has given them a certain amount of money that is left over from the Home Depot virtual egift. The remaining amount can revert to the giver after certain conditions are met. The system can alternatively apply those funds as a refund or bill reduction on a credit card statement that is not tied to a specific transaction, but is instead simply a deposit.

FIG. 6 illustrates a series of steps 600 associated with the management of virtual egift funds. Step 602 includes selecting a policy for a virtual egift. This can occur via a default mode or a user selected mode to establish a certain policy or schedule for the distribution and use of the virtual egift. One example of the policy is that the recipient is given six months in order to use the virtual egift via their credit/debit card at a selected merchant or at a brick and mortar merchant location. In one variation, the system establishes a default policy for virtual egifts. However, specific items, merchants, givers, recipients, or other entities or aspects can also include default and/or mandatory policies. The system can layer the different policies for a virtual egift. For example, the egift giver can impose a policy limiting the virtual egift to clothing. The merchant can impose a policy limiting the virtual egift to within one year of the date of the virtual egift, and the credit/debit card issuer can enforce a policy that money spent with the virtual gift does not apply to a frequent flyer or other rewards program. The system can combine each of these policies and enforce each of them on the virtual egift. Each policy can include an expiration date after which the policy is not enforced. In one aspect, a minimum threshold of policies must be satisfied to trigger the application of the egift funds, such as a transaction fulfilling at least 3 out of 5 policies in force. The system can notify the virtual egift recipient of the various policies when the card is received, when the virtual egift is redeemed by making a purchase with the credit/debit card or at any other time. Merchants can also add incentives to those remaining amounts. The merchants would like to have the recipient come back to the store. So if $12.50 remains on the virtual egift, the merchant can offer to increase the amount to $15 or $20 to entice the recipient to come back. Such an offer can be for the next three weeks. As can be seen, a variety of was exist to use remaining amounts on virtual egifts and notifications with changes to encourage recipients to return to the merchant.

The system includes a trigger associated with the use of the funds in step 604. The trigger can be an actual transaction using the credit/debit card in which the funds have to now be applied and released for a transaction. The trigger can also be an internal time frame in which the funds have not been used or some external event. The trigger can include a series of triggers. In an incremental trigger example, each trigger in the series should be satisfied before the next trigger is evaluated. In a partial set of triggers example, a predetermined partial subset of the set of triggers will satisfy the set, such as “any single trigger” or “each of triggers 3, 4, and 8”. In an entire set of triggers variation, every trigger must be met in order for the whole the series to be satisfied. Accordingly, the trigger can be after a period of time in which the recipient has not selected to use the funds. The system can arrange triggers to achieve complex functionality. For example, the system can arrange a first set of triggers indicating a date range of “January 1-January 31” and the merchant “Home Depot”, a second set of triggers indicating a date range of “February 1-February 28” and any of the merchants “Home Depot, Lowe's, Ace, and Menards”, and a third set of triggers indicating a date range of “March 1 or later” and no restrictions on merchant. The trigger can be a recipient, giver, or some other person's and/or device's location or some outside event for a specific purchasing transaction. This set of triggers provides a set of generality levels so that in January the egift is applicable to a specific merchant, and if it is not used in January, then February the egift is applicable to a specific set of merchants, and if it is not used in February, then the egift is generally applicable to any merchant. One trigger can lead to another trigger. This incremental triggering approach could allow for the giver to receive awards when a purchase is made at a preferred store. For example, the giver could receive a certain dollar amount or discount from a preferred store when the recipient redeems his virtual egift at the preferred store. The giver could receive a 10% coupon for Home Depot when the recipient redeems an egift of $200 or more. This scenario is a simple example and other variations on a giver reward program exist. The last step involves releasing or applying the funds 606 to a transaction which, as noted above, can either be releasing or using those funds for a particular purchase or can involve transferring those funds directly to the recipient account or to some other location. Then the policy can include a series of triggers that cause the system to apply funds according to the policy.

Virtual egift user interfaces can enable the giver to blend a physical gift card with a virtual egift. Often for birthdays, Christmas, Hanukkah or any gift giving the giver desires to have some physical object to wrap up. The system disclosed herein can enable a scenario where the giver buys a physical gift card having a code or a bar code. This can be a special gift card or a normal gift card purchased. Then the giver can enter the code or scan a bar code in an interface to identify that physical gift card. This can essential make the physical gift card the “giver.” Then the giver can identify the recipient as disclosed herein. The interface can therefore identify the giver account as the physical gift card and the recipient with the associated recipient account. Absent any other user interaction, the policy for the recipient redeeming the gift card can be based on the physical gift card. For example, if the physical gift card was for a merchant such as Olive Garden for $50, then the policy will apply accordingly, with any additional settings such as how to handle remainder amounts. The giver may be also able to modify the policy for the physical gift card.

Under the above scenario—the giver can actually give the physical gift card for a present. However, the giver can then explain or send a message or communicate in some way that the physical gift card has been associated with the recipient credit/debit account and all the recipient needs to do is make the purchase at the merchant using their credit/debit card. The recipient can therefore throw away the physical gift card since it is no longer needed. This achieves all the goals of being able to give a physical gift for the moment, but then handle the possibility of losing the physical gift card or forgetting that money is still on the card since the policy is applied to monitor the recipient purchases and is applied for that gift card. Any recipient of a physical gift card could also associate the gift card with the credit/debit account in the same manner.

eGIFT Management Portals

The disclosure turns to a discussion of management interfaces for virtual egifts. FIG. 7 illustrates an example portal 700 in which users, including givers and recipients, can manage their various egifts. A network-based server and/or a local server can provide the portal 700 in which the recipient receives a number of different virtual egifts. The prior art approach for dealing with gift cards is to simply carry physical cards around in one's wallet or store them at home or elsewhere. The remaining amount on those particular gift cards is easily forgotten and not always easy to retrieve. This ultimately leads to wasted funds or the funds can revert to the merchant through fees or inactivity. It is almost impossible for the recipient of the gift card to remember how much money remains on the cards, especially if multiple gift cards are received at the same time. Accordingly, using the system disclosed herein, a recipient can manage, identify, and view a variety of virtual egifts all in one location. Portal 700 illustrates all of the virtual egifts for one recipient or for one payment mode (such as a checking account, Visa credit card, or PayPal account). Information 702 identifies a virtual egift from George to Rachel for use at Home Depot for $175. Information 704 identifies a virtual egift from Ryan to Rachel for use at Best Buy with $42.17 remaining. In this case, a purchase of Boom Blox Wii on Sep. 17, 2010 is identified and thus the history and use of that virtual egift is presented. Information 708 identifies a virtual egift from Linens‘N’Things for $25 which is identified as expiring on Dec. 31, 2010. This virtual egift is actually one directly from a store (i.e., a merchant is the giver) and has an expiration date and such expiration date is identified on the report 700. Such merchant generated egiftss can be automatically or manually generated based on purchase history of the recipient, combined with inventory or other data.

In this portal 700 interface, the recipient can easily review and browse information about all of the various virtual egifts that they have received and thereby easily be able to manage these virtual egifts, change policies if allowed, merge virtual egifts, regift, and obtain information about the use of these virtual egifts. This interface can also include a menu for additional options, such as regifting, merging, sending a thank you message to the giver, and rejecting or returning the virtual egift to the giver. The recipient can even add money to his own virtual egift. The recipient can regift a received virtual egift even if the recipient has already purchased a desired item, Boom Blox Wii, from Best Buy using the virtual egift from Ryan 704 and has no further need for the remaining balance on the virtual egift. The portal can provide a way for the recipient to identify a regifting recipient and transfer all or part of the remaining balance to the regifting recipient as a new virtual egift. The recipient can also add an amount to bump up the amount to a round number. For example, the recipient can add $7.83 to the remaining balance of the Best Buy virtual egift 704 to make an even $50 virtual egift for a new recipient. The portal 700 provides the recipient with an easy mechanism to view and manage each virtual egift according to policies associated with each virtual egift. The recipient can even be allowed to override the policies in some instances, such as for a fee or after a threshold duration, such that the system handles the egift funds differently for the new recipient. Such opportunity may be set by the giver, system, or any appropriate entity. All the options disclosed herein for a giver are available to the recipient (as a new giver) who is regifting all or a portion of a received virtual egift to a new recipient.

FIG. 8 illustrates an example portal 800 for use by a giver. In one embodiment, both portals 700, 800 are integrated into a same web interface so that a giver can manage all received and sent virtual egifts in one location, but the portals 700, 800 can also be completely separate. Just as a receiving party can have a portal as shown in FIG. 7 to identify all of the received virtual egifts, a portal 800 can be presented for those who send virtual egifts. Here, information such as found in rows 802, 804, 806 and 808 can identify the date a virtual egift was sent, the recipient, the amount, the merchant, the current status, and additional optional actions which can be taken, such as send a message, send a reminder or suggestion, or any other additional communication option for the giver to communicate with the recipient. Accordingly, the system can present other options for such communication or using other communication means. For example, the interface can include a telephone in which the giver can directly call, such as via Voice over IP (VoIP) from this interface to the recipient and talk about the virtual egift or any other topic. In one variation, the portal 800 can include an option to send a copy of the virtual egift again in a year or at some other interval. In the case of birthdays, the option to send again can include the ability to increase the amount by a specific dollar amount, based on inflation, or based on some other criteria. In one embodiment, the virtual egift can be triggered by some behavior, such as a recipient earning straight As on his or her report card. Such data can be defined by a social network or other general data source. The system can monitor the appropriate information source for fulfillment of the trigger, the system can activate the virtual egift and/or send a notification to the giver and/or recipient that the virtual egift is active. Further, the system can send a notification of the trigger to the giver for approval before activation.

FIG. 9 illustrates an example interface for managing policies associated with sent and/or received virtual egifts. In the interface 800 of FIG. 8, the giver can click on the row 802 for Tom Jones to expand a list 902 of available or applicable policies. The list can be a compilation of different policies from different sources or a single policy encompassing each presented aspect. This interface is exemplary can be interchanged for other interfaces. This interface provides a list of valid merchants as a policy, which the giver can revise, add to, or remove before or after the virtual egift has already been sent to the recipient. The interface provides a way to manage the expiration date. Some policies, such as the “split virtual egift” policy are controllable only by a recipient, so the giver interface disables and/or does not display these policies. Likewise, a giver interface can provide the giver a way to manage giver-controlled notification policies. Some aspects of notification are controlled by a third party or by the recipient, so they do not show up in the giver's interface. After the virtual egift has been sent, the giver can modify the virtual egift by applying promotions. Some of these promotions may not have been available at the time the virtual egift was sent, but become available at a later time. At this later time, the giver can include these promotions in the virtual egift. The giver can also indicate at any time that any promotions or class of promotions can be applied automatically when or if they become available. The recipient management interface can provide a similar corresponding way to view, add, manage, change, and remove policies on received virtual egifts.

FIG. 10 illustrates an exemplary method for managing virtual egifts. A system configured to practice the method identifies a user, which can be a giver and/or recipient of a virtual egift (1002) and retrieves a list of pending virtual egifts associated with the user, wherein each virtual egift in the list is associated with a payment mode of the user such that upon the recipient using a recipient payment mode to make a purchase, an amount of money associated with one of the pending virtual egifts is applied to the purchase (1004). The system retrieves current status information for the list of pending virtual egifts (1006). The system presents at least part of the list of pending virtual egifts to the user (1008). Users can access this information via a virtual egift management portal such as a web site, smart phone application, automated speech interface, and so forth. In one aspect, the interface sorts the virtual egifts. For instance, the user can sort the virtual egifts by sent and received, date of the virtual egift, amount available or outstanding, merchant, friend, policies, etc. Through the interface, a giver can modify aspects of a sent virtual egift, such as increasing the amount on the virtual egift, changing the policies associated with the virtual egift, adding or removing payment modes with which the virtual egift is associated, etc. The virtual egift management can be split into a section for sent virtual egifts and a section for received virtual egifts. The management interface can display the policies associated with each egift, links to websites or applications of the financial institution providing the payment mode, such as American Express, Visa, MasterCard, a local bank, and so on.

eGIFT Promotions

The disclosure now turns to a discussion of adding promotions to a virtual egift. FIGS. 11A and 11B illustrate interfaces for a giver to add promotions during a creation event of a virtual egift, but a recipient can also view and accept promotional offers when the card is received, when managing a received card, when redeeming a received virtual egift, when reviewing remaining amounts, and/or at any other suitable time. FIG. 11A illustrates a window 1100 for additional accessorizing, including promotions, or upselling of the virtual egift. The giver, George, wants to give $50 to Rachel for use at the Sizzler restaurant. The system can identify different available promotions to “accessorize” the virtual egift. Here, one promo 1102 is from American Express. A giver can select the promo 1102 with a checkbox or other input to require Rachel to pay via American Express and thus get an extra $5 added to the egift amount.

It is presumed in one example that the system has already gathered information about Rachel and is aware that Rachel has an American Express card that can be selected. A promotion 1102 provides for an additional level of competition among credit card issuers. Rachel has a MasterCard, Visa and American Express credit cards. Clearly, American Express or any of the other card issuers desires to push more business their way for fees, rewards, loyalty, or other reasons. Card issuers can offer an additional bonus amount of money if the giver selects a card from that issuer. Therefore, if the giver selects promo 1102 then the ultimate notification that the system sends to Rachel can include the requirement that in order to redeem the virtual egift, Rachel must using her American Express card at Sizzler. The system can optionally notify recipient Rachel that an extra $5 is being added by American Express to the virtual egift amount. However, appropriate communication is made to instruct Rachel to use the American Express at Sizzler to redeem the virtual egift. In this aspect, American Express either can increase the virtual egift balance or apply a $5 credit to Rachel's American Express bill when the virtual egift is used.

Similarly, the giver can limit the use by Rachel of the virtual egift to a weekday. Promo 1104 indicates that if Rachel uses the virtual egift on a weekday that he would get a free dessert. That box can be checked as a promotion by Sizzler in order to drive the recipient's behavior to come to the restaurant as a certain time, perhaps when it is normally slow. A communication would then have to be made to Sizzler, in which once the American Express (or other card) is used to make a purchase on the appropriate time (Monday-Thursday) and in the evening, then the dessert that would be ordered would be given free. Sizzler, or the merchant, either can increase the virtual egift balance to cover the free dessert or handle the promotion side by applying the discount at the register or point of sale without affecting the virtual egift balance.

FIG. 11B presents a widget in which the system has identified the giver as George, the recipient as Rachel, and the merchant as Olive Garden. The system has identified that Rachel typically uses, has used, or is eligible to use one of two payment mechanisms for purchases at Olive Garden: a Visa and a MasterCard. The opportunity presented to George in FIG. 11B enables George to choose between the Visa and the MasterCard. As is shown in the widget, Visa is offering an additional $2 to the virtual egift and MasterCard is offering an additional $1 to the virtual egift. The Olive Garden can offer an extra $10 if it is limited to lunchtime on Saturdays. This presents an opportunity for the credit card issuers to upsell or encourage the giver to select a particular card for redemption of the virtual egift. The giver, George, can click the send button to complete the transaction. If George does not select Visa or MasterCard, the system can inform George that the most common card used by Rachel is the Visa card and that the Visa card is the default if no specific card is selected. The system can apply various algorithms in order to present this selection of Visa or MasterCard to the giver. For example, if the virtual egift is for dinner at P.F. Chang's restaurant, the information presented to George can indicate that Rachel typically uses her MasterCard for restaurants and other such social or like purchases.

If Visa wants to shift that usage from MasterCard to Visa, Visa may be more willing to upsell the virtual egift and offer more money in addition to the virtual egift amount. In this respect, a system practicing this aspect of the disclosure receives information about the giver, the recipient including credit cards or debit cards as well as purchasing history associated with those credit cards and debit cards. An algorithm compares the purchasing history with information associated with the virtual egift and the scope or the context in which the virtual egift can be redeemed. The algorithm can then present to the giver options associated with the recipient's accounts that are tailored to the virtual egift context and the purchasing history of the recipient. The system receives a selection from the giver of a selected payment mechanism (or no selection, which defers to a default mode) and then carries out the processing of the virtual egift according to mechanisms disclosed herein.

FIG. 12 illustrates an example method of the promotion-related user interfaces of FIGS. 11A and 11B. The system identifies a creation event of a virtual egift (1202) and identifies an applicable promotion to the virtual egift (1204). Then the system presents the applicable promotion to a user, either a giver or a recipient, associated with the creation event (1206). The system receives input from the user indicating acceptance of the applicable promotion (1208). Then the system can incorporate the applicable promotion into the virtual egift such that upon a virtual egift recipient using a recipient payment mode associated with the virtual egift to make a purchase, a virtual egift amount of money is applied to the purchase according to the applicable promotion (1210). The system can present the promotions to a giver and/or a recipient. For example, when a giver is creating the virtual egift, the system can present a first promotion, and when the recipient receives or after the recipient has received the virtual egift (or notice of the virtual egift), the system can present a second promotion which may be the same as or different from the first promotion.

A second example involves rewarding the giver when a recipient redeems the egift at a preferred store or for a preferred service. For example, when the recipient redeems the egift at Home Depot instead of letting the gift transfer to a dollar amount after a specific time frame, the giver earns a reward, such as a $5 virtual egift to Home Depot. The giver may choose to redeem it himself or give it to the same or different recipient that redeemed the original egift. Not only does the recipient receive a benefit in this scenario, but the giver also receives a benefit when they give a virtual egift. Rewarding the giver provides the merchant a way to seek additional customers, i.e. the giver, to reward loyalty, and to track gift purchases in a more precise way. In this way, a healthy relationship can exist between a virtual egift giver and a merchant where all parties (the giver, the recipient, and the merchant) benefit from the giver giving a virtual egift to the merchant's store. While promotions can be handled manually, an automated promotions infrastructure can allow merchants, credit card issuers, and other potentially interested entities to set rules, policies, thresholds, and/or other guidelines for automatically generating promotions in a much more targeted and responsive way. The giver can build up over time rewards for giving virtual egifts. Entities offering promotions can manage these promotions and associated policies, rules, and so forth via a promotion interface. The promotion interface can also include analytics, statistics, billing, customer tracking, customer loyalty, overall retail performance, individual transaction performance, and other reports.

The system can also receive from a giver an identification of a recipient and a dollar amount for a virtual egift. The system also receives from the giver an identification of one of a credit card/debit card issuer and a time frame associated with use of the identified card. Promotions can be time-sensitive, lasting for a limited duration. The system can also present to the giver various additional upselling items associated with one or more possible selections. The system then manages the redemption of the virtual egift based on the received conditions in the policy set forth above.

Blanket upselling or offers can be provided with the virtual egift approach disclosed herein. For example, assume that Olive Garden, in their calculation, desires to bring more people in who have virtual egift outstanding for their stores. The company can simple provide an announcement or an advertisement that states that anyone having a virtual egift with money still on the account for the Olive Garden will receive an extra 10% off their meal if they come in the next week. The policy governing the Olive Garden egifts can be centrally modified to handle such a promotion for everyone coming in and using their credit/debit card account. Such policies can also be modified on a store or region basis. For example, a study may show that there are an unusual number of virtual egifts for one city that are not being used. The scope of the offer can be for residents of that city. The policies for those virtual egifts based on geographic location (which can be determined by address of the recipients, address of the recipient account, or other factors) can be modified for such a promotion. Then if someone with an Olive Garden virtual egift from a neighboring state uses their virtual egift, they may not then have that particular promotion applied to them because they do not fall within the regional scope of the offering.

The above idea provides an additional feature of how policies can be managed to upsell or add offerings to a single virtual egift or groups of virtual egifts. The offerings can be divided in any manner. There can be a “female” night at the merchant, or all patrons over 50 years old can get a discount. Such data can be identified in connection with the recipient account and so applied. Any personal or other kinds of data can be associated with a recipient account and therefore be used to modify policies or make additional offerings. In another example, the offering may be for any recipient who traveled to Mexico in the last year (and perhaps used their credit/debit card on the trip) gets a special discount on sporting goods. The activity of the recipient account can be tracked to trigger whether particular individuals comply with the offering.

All such recipient offerings discussed above also apply to the giver and giver accounts. Therefore, the offerings can be based on a study that givers of gift cards or virtual egifts have been decreasing over time and that merchants desire to increase the numbers based on geography, demographics, usage history, or any other type of data that can be applied to a giver account. Thus, an example offering could be that any giver who went to a professional basketball game this year, (and perhaps purchasing their tickets using their credit/debit account), will get an extra $3 added to any virtual egift given in the next month. The system can obtain any such data about the giver or recipient through social networking, personal input to a website, tracking financial transactions, third party entry of data, or any other database. Such offerings for givers and/or recipients may also come from external events. For example, the offering may be if the Yankees win the World Series, then all virtual egift givers will have an extra $2 applied for all New York restaurant virtual egifts for the week after the game to celebrate. The combinations of triggering events for offerings and the scope of offerings is widely varied. The basic approach is that promotional offerings can be carefully crafted and controlled on any type of basis for a particular group of people to drive them to either purchase virtual egifts, redeem virtual egifts, regift virtual egifts, or perform any event associated with virtual egifts as disclosed herein.

Such events could even include concepts such as modifying the policy associated with their virtual egifts. If a recipient has a virtual egift that is not tied to any merchant, a promotion may simply be that if that recipient will transfer that virtual egift to be only redeemable at the merchant establishment, then some value is added such as a free dessert or an amount of money added to the virtual egift.

An example of an external event is where the system may monitor web activity and determine that in a particular region, the number of web hits for certain cites such as Home Depot are on the rise or out of normal usage. The system can treat this as a trigger or be triggered by this detected data and cause a promotion accordingly. The promotion may be to all those in the region who have virtual egift money not yet used at Home Depot to come in and receive an additional value for using the virtual egift during a specific time. Such external events may include other things such as weather reports. If a storm is coming, this event can trigger a promotion to those with virtual egifts to Home Depot to get a discount when redeeming the virtual egifts in preparation for the storm.

To accomplish the functions above, detecting systems for the various input can be used, which can then communicate with policy implementing or promotion intelligence engines which determine a particular promotion and scope of distribution. Each individual may receive as part of a promotion a tailored promotion given various factors such as purchasing history, amount left on their virtual egift, income, circle of friends, policy for that card (such as 1 week left before it is going to expire or be distributed to the recipient account, or 6 months left), etc. The promotion can be therefore varied for individual virtual egifts and the policies associated with the virtual egifts or other factors.

In general, promotions can be triggered by manual input or automated input that is internal to the use of the virtual egift or external and/or based on group activities or trends. A promotion engine will receive the various input, compare the input to the group of outstanding virtual egifts and/or the policies of those virtual egifts. Data associated with the recipients and/or givers of the virtual egifts can be received. The promotions engine can then, based on the data, generate a promotion that has a high likelihood of encouraging recipients and/or givers to act to further use or give virtual egifts as urged by the promotion.

eGIFTS and Social Networking

The disclosure now turns to a discussion of virtual egifts and social networking. The virtual egifts identified herein also advantageously can be used in specific verticals and social networks. For example, FIG. 13 illustrates a Facebook page 1300 in which a virtual egift can be applied. Window 1302 includes the typical Facebook information. The right portion of this page illustrates an example presentation of various pieces of information that can help the giver, a Facebook user who is currently logged in to Facebook, to give virtual egifts in an efficient manner. Personalized information from Facebook about a giver, as well as various friends or family members identifiable via Facebook, other social networks, email contact lists, applications running on the Facebook platform, a virtual egift sent/received history, a calendar of upcoming events associated with friends and/or family, and/or other sources can be used to present opportunities to give a virtual egift and/or a predicted set of virtual egift recipients in window 1300.

For example, birthdays 1304 (or other special events such as anniversaries, graduations, engagements, weddings, holidays, and so forth) can be presented in a certain order in which Mom's birthday 1306 is identified as being January 6th, the system can present a suggested option of Olive Garden and $20 as a virtual egift, in addition to the Send button. Because the system predicts information based on your friends and family, the virtual egift interface can present a “One-Click” virtual egift. It is assumed that Mom has previously been identified in the Facebook system, the system knows who the giver's Mom is, and the system can appropriately identify Mom's account such that system can process the $20 from the giver's account to the Mom's account when a purchase is made at the Olive Garden using an existing credit/debit card. Where Facebook or an environment account does not have account information, then the system can communicate securely with a system that has the needed account data and/or can carry out the policies for virtual egifts. In this respect, a Facebook environment only needs sufficient data for the giver, recipient, account, and policies, to transfer that data to a system that can carry out the virtual egift process.

The birthday list 1304 can include other entries. One entry 1308 identifies June Smith has an anniversary coming up and suggests a $25 virtual egift for Cinema 10. The system can generate other suggestions upon request based on an analysis of a number of factors, such as previous virtual egift history, previous use of Facebook, previous amounts given via virtual egift, what others have already given June Smith (virtual egift amounts and virtual egift merchants), and so forth. The system can identify and correlate this information in order to present suggestions in window 1300 for giving virtual egifts from the giver.

The birthday list 1304 includes an entry 1310 for a $20 gift certificate for Sister through Amazon.com. Accordingly, the recipient can use that virtual egift in their next purchase on Amazon.com. The recipient does not need to keep track of and enter any gift card codes inasmuch as Facebook and/or other mechanisms appropriately identify the “Sister” to the giver such that the remaining processing can easily occur. This eliminates the need for the sister to enter a long alphanumeric code to receive a $20 virtual egift associated with a transaction such as any purchase on Amazon. The display informs the giver that last year the giver sent a $20 Amazon virtual egift to the recipient. This information can help the giver determine an appropriate amount.

A social network site, such as Facebook, MySpace, Twitter, or the like, can provide individual “one-click” buttons to give a virtual egift to a giver directly on the giver's profile page. For example, if George browses to Rachel's Facebook page on or shortly before her anniversary, the Facebook page can include a virtual egift button that George can click to give her a $20 virtual egift instantly based on both of their account information available to Facebook. Inasmuch as the identity of the giver and recipient are already known, the system only needs to tap into the recipient account data and carry out the virtual egift polices. In one alternate embodiment, in conjunction with the “one click” option, the giver can click to expand and edit the virtual egift options. For example, George can click to expand the “one click” virtual egift, increase the amount from $20 to $40, and change the merchant from amazon.com to Macy's.

Scheduling eGIFTS

FIG. 14 illustrates an interface 1400 that enables a giver of a virtual egift or cards to schedule various recurring virtual egifts. For example, a giver wants to schedule virtual egifts for significant events of certain close relatives or friends. The events can be scheduled for recurring events, such as a yearly birthday virtual egift or at some other interval such as an anniversary virtual egift every five years, or for one-time events such as a wedding, birth, or graduation. Row 1402 illustrates a schedule for the giver's Mom whose birthday is on April 1st. The giver can select various options such as reminder and preview, choose a dollar amount, choose identification of the card to be used by the recipient to redeem the virtual egift, and a merchant for redemption. Messages can be added such as “Happy Birthday” which can add to the personal nature of the communication. The giver can then schedule virtual egift email to be communicated on a certain date in advance of the birthday. The reminder option instructs the system to remind the giver to send a virtual egiftfor a particular recipient and/or event. The reminder can include a virtual egift history for that recipient or event.

Further, the system can provide an optional pre-populated virtual egift request for the giver to confirm to initiate the virtual egift. The preview option is a variation in which the system sends a preview to the giver before sending the actual virtual egift. The giver does not need to do anything to confirm or approve the scheduled virtual egift. However, the giver can, based on the preview, transfer funds between bank accounts to cover the scheduled virtual egift, or log in to the virtual egift scheduler interface (or directly in the preview communication) to change any settings associated with the scheduled virtual egift, including cancelling the scheduled virtual egift. For example, the system can present a graphic or multimedia presentation to the giver illustrating the policy for that virtual egift. Changes to the policy would be shown in the graphic.

Row 1404 illustrates an example scheduled virtual egift for Dad's birthday. Row 1406 illustrates a scheduled virtual egift for Sister's anniversary at a certain date with a reminder box checked as well as the preview box checked. The amount is for $50 and is for a novel by John Grisham. The identification of what the virtual egift is used for is not limited to a particular merchant but to a particular product regardless of the merchant providing the product. Whether the purchase is at a brick and mortar store or online, wherever there is a mechanism of identifying the item purchase, this virtual egift would apply to that particular item. After the purchase of the novel, the system can apply the remaining funds, if any, to any purchase without limitations or transfer the remaining funds back to the giver, for example. The system can provide a message in the virtual egift, in connection with a communication to the recipient associated with the virtual egift, and/or on a store receipt.

Row 1406 also illustrates another point in which the scope of the virtual egift can be modifiable. A typical physical gift card applies to a store or close group of stores. Because the recipient redeems the virtual egift by simply using a Visa card online or at a merchant store, the system can gather additional information about the purchase. Therefore, a grandfather gives a virtual egift of $500 to help his grandson simply buy a car. There is no particular merchant but the scope of the virtual egift is based on the general description of an intended purpose for the virtual egift. Therefore, as the grandson goes out and purchases a car, the system can process the $500 in any number of ways such that the virtual egift is applied to that particular transaction for the grandson. In another example, a mother gives her daughter a monthly recurring virtual egift of $100 for use at college. The mother can place a location-based restriction on the use of the virtual egift to within 20 miles of the college campus and can also limit the use of the virtual egift to purchases of text books, food, toiletries, and gas, regardless of the merchant or vendor. These types of more complex conditions or limitations on the virtual egift are unavailable with traditional physical gift cards. Thus, a variety of different ways exists for managing the scope of transactions to which the virtual egift is applied.

Combined Virtual eGIFTS from Many to One

The disclosure turns to a discussion of another aspect of this disclosure, namely a group virtual egift. FIG. 15A illustrates an exemplary user interface 1500 for giving a group virtual egift to Tom for his birthday. In one example implementation, a virtual egift is a way for multiple givers, such as friends, co-workers, or family members, to each contribute a small amount to a virtual egift for one recipient. Thus, one friend contributes $2, another friend contributes $3, another friend contributes $1, a spouse can contribute $20, etc. The system takes all those contributions and combines them into a single virtual egift for the recipient. This can be applied to weddings, honeymoons, baby showers, retirement gifts, and so forth.

While a group virtual egift can operate in many kinds of environments, the examples discussed herein are in the context of a social networking environment. For example, if Rachel's birthday is coming up, Facebook presents to all or part of Rachel's friends a popup window 1500 that includes information such as a title, a total amount of money collected from various givers in a group virtual egift, and other information such as the largest giver. The largest giver is George who has contributed $10 to the virtual egift. The display 1500 can include a number of total contributions as well. The system can analyze the relationship between the virtual egift recipient and the giver viewing the display to generate a suggested amount to contribute to the virtual egift. The relationship is a business acquaintance and the suggested amount is $10, but the system can suggest other amounts for personal or other types of acquaintances, family members, co-workers, and so forth, based on a variety of factors. The window 1500 can include a “one click” button to give the suggested (or other) amount, or the window 1500 can include a separate field or input element 1516 where the giver enters a certain dollar amount.

The group virtual egift works in the context of the present disclosure because the system gathers the various moneys into a single amount and gives that amount to the recipient as a virtual egift. Therefore, following the development of a virtual egift, the system can present the recipient Rachel with an email or other communication that lists the 22 people that have contributed to a virtual egift of $61. There may be no identifiable scope to this use and it may immediately go into Rachel's Visa account or debit account. In one variation, each giver votes for a restaurant, merchant, vendor, or a particular use. The givers' votes can have a one person, one vote weight or the vote weights can be associated with the amount of money contributed to the virtual egift. The social network, such as Facebook, can present a “game” to givers where each is encouraged to contribute more money to “beat” other givers for first place. One variation to encourage this type of game is to allow only the top contributor (or top N contributors) to select the ultimate virtual egift. In one aspect, the system can establish a contribution period during which social network friends can contribute to the group virtual egift. In another aspect, the system resides outside the actual social network and can implement the group virtual egift using contributions from multiple sources, such a virtual egift web portal, other social networks, kiosks, and so forth. At the end of such a process, the resulting virtual egift can be for $71 for dinner at the Olive Garden which was what most of the contributors desired to define as the scope of the virtual egift. A group dynamic can greatly enhance the experience of generating and compiling a virtual group egift.

A human can initiate the group virtual egift and become an organizer for the virtual egift. The organizer can set the terms of the egift, the contribution period, and other aspects associated with the virtual egift. The organizer can also filter messages to the recipient from the other contributors associated with the virtual egift, and so forth. The organizer can decide, for example, whether to enable voting for the virtual egift merchant and can manually select a particular vendor, item, or other restriction for the virtual egift. In one variation, the social network is the “organizer” and can maintain that role throughout the virtual egift creation process or can hand off that role to a human participant. In another variation, the highest contributor automatically assumes the role of the “organizer”. The system can hold contributed money in a third-party account until redeemed, transferred to the recipient's account, or otherwise used by the recipient. In the event that a group egift is rejected or cancelled before the system completes the process, the system can refund the contributed funds to the contributors directly and optionally notify them of the failed virtual egift.

The system can further provide notifications in connection with a group virtual egift. For example, each contributor to the virtual egift can include a personal message with his or her contribution. Then when the system notifies the recipient of the virtual egift, the notification can include a list of all the contributors and their respective messages. The messages can be text, images, audio, video, documents, and/or other formats. The system can provide a notification to the recipient via email, SMS, web site link, Facebook post or other social network action, a printed and mailed physical greeting card, and so forth. Similarly, when the recipient uses the virtual egift to make a purchase using their Visa card, MasterCard, PayPal account, or other recipient payment device, the system can notify all or part of the contributors that the virtual egift has been redeemed, what was purchased, etc. The recipient can control those notification settings, such as who gets which notification, who gets a notification at all, what they will see, and so forth. Further, contributors can opt in or opt out of these notifications.

One example of a group card in operation can be a bereavement group egift. If a spouse passes away, a bereavement email can be sent by a friend with a egift request. People can easily each give amounts to the surviving spouse who can get a notice of how much is available for use on their credit/debit card at a very difficult time. Thus, various types of group egifts can be applied in the system. This makes redemption very easy for those in need.

FIG. 15B illustrates an example architecture 1520 for interfacing between online merchants, social networks, and banks that can be used for individual or group virtual egifts. This architecture 1520 allows a merchant 1524, such as Amazon.com, with established user accounts 1526 with the merchant 1524 to communicate with a social network 1528, such as Facebook or MySpace, with established user accounts 1530 with the social network 1528, for the purpose of processing (i.e. giving, receiving, managing, and redeeming) virtual egifts. Further, a control engine 1522 can interact with the social network 1528 and/or the merchant 1524 to guide or control virtual egift transactions. The control engine 1522 can communicate with a bank 1532 or other financial institution holding a group of bank accounts 1534 and a third-party account 1536 for holding funds in some virtual egift scenarios. Some bank accounts 1534 correspond to the various accounts 1526, 1530 in the social network 1528 and/or the merchant 1526. The architecture 1520 can provide a user interface for the users on the social network, merchant, and/or control engine to manage virtual egifts. The social network 1528, merchant 1524, control engine 1522, and bank 1532 can communicate with each other via established APIs for purposes relating to creating, delivering, notifying, and predicting related to virtual egifts.

For example, multiple givers on the social network 1528 who each have a social network account 1530, want to give a virtual egift good for a purchase at the merchant 1524 to a recipient who also has a social network account 1530. The social network 1528 communicates this information to the control engine 1522 via the API. The control engine 1522 communicates with the bank 1532 (which can represent one or more separate financial institutions) to identify bank accounts 1534 associated with the respective social network accounts 1530 of the multiple givers. The control engine 1522 reserves, withdraws, or holds funds for the virtual egift from the identified bank accounts 1534, such as in the third-party account 1536, according to the type of account it is (e.g. credit or debit). The control engine 1522 can also identify the recipient's account 1526 at the merchant 1524 and credit the virtual egift amount directly to that account. The control engine 1522 can also associate any policies and/or triggers with the virtual egift. Then the control engine 1522 optionally sends a notice to the recipient of the virtual egift via the social network 1528 or other communication modality. The recipient of the virtual egift can then shop at the merchant 1524 and the control engine 1522 and/or the merchant 1524 applies the virtual egift to transaction(s) according to the policy and/or triggers established.

FIG. 16 illustrates a method embodiment of this approach. In one variation, the system receives an egift for a recipient from a group of givers (1602). Then the system withdraws a group of egift amounts of money from accounts, or reserves credit available, of the group of givers (1604). The system identifies a recipient payment mode (1606). Then, upon the recipient using the recipient payment mode to make a purchase, the system applies at least part of the group of egift amounts of money to the purchase (1608). The group of givers can be on a same social network, for example, or spread over multiple platforms, such as social networks, merchant environments, banks, and so forth.

Intelligent Transitions for eGIFT Options

FIGS. 17A-17D illustrate an aspect of this disclosure associated with intelligently transitioning egift options, including virtual egifts, at a web shopping portal such as Amazon.com. Here, a window 1700 illustrates a giver George 1704 who is shopping on Amazon. A particular context 1702 is arrived at in which an item is being viewed for purchase on Amazon. The system can present an interface to George for giving a virtual card 1706 to somebody. The interface can include a widget 1708 to enable George to select a particular person as a recipient of a virtual egift. George can identify in other fields a particular amount of money, a message field for the recipient, an amount of money, and/or other options relating to the virtual egift. All of this information can be combined in a widget 1708 or a small window that the giver can use to give a particular egift to a particular recipient. The fields in window 1708 can be prepopulated based on the current context of George's searching within Amazon. For example, if George has arrived at a television set that is $800 to buy, then that amount of money can help to prepopulate information 1708 such that the virtual egift that is ultimately generated from George can be associated with the particular product or service that is being searched on Amazon. Therefore, the virtual egift can include a specific purchase of the item for the recipient or can include a presentation of a more standard virtual egift for a certain amount of money. In one aspect, when a giver clicks Purchase 1710 in FIG. 17A, the virtual egift can be created and transferred to the recipient either through an Amazon account generally or through one or more specific credit card that the recipient has on file at Amazon. In other words, if George selects to give a virtual egift to Rachel, and Rachel has a Visa that is used in her account on Amazon to purchase items, then the virtual egift from George can be processed through Rachel's Visa stored in her Amazon account. Otherwise, the virtual egift can be redeemed directly via the Amazon account and not using the recipient's debit or credit card account.

FIG. 17A therefore illustrates an approach in which a virtual egift interface can be presented that is dynamic based on a level of surfing an internet page. If FIG. 17A represents an initial beginning of a search at Amazon in which the giver has just logged in, then the presentation of a window 1708 can represent an opportunity for George to give a virtual egift to somebody just for use on Amazon. This is because the context in this scenario is only based on being in the Amazon environment. Assume that George searches for the garden section and browses to the interface shown in FIG. 17B.

FIG. 17B illustrates a dynamically modifiable virtual egift interface at a lower level. Here, assume that window 1712 represents a search such that the giver is in the Amazon garden environment 1714. Here, various garden tools and supplies are available. The widget 1718 that can be presented to give a virtual card 1716 can adapt to this context. As can be seen in window 1712, shovels, rakes and hoses that are available in the window 1718 can adapt such that the giver can select as the scope of the virtual egift and can be dynamically modified such that garden items defines the scope of the virtual egift. Therefore, when the giver uses field to select a recipient for the virtual egift, and the amount is entered in field, when George hits Purchase in field 1720, then the virtual egift that is given can have a dividable scope of garden items within the Amazon environment. Further, the system can analyze the contents of the window 1712 and generate a one-click button 1722 to create a virtual egift for Dad or some other friend, relative, or acquaintance. George clicks on the shovel portion of the garden section and browses to the interface shown in FIG. 17C.

FIG. 17C illustrates another layer. Here, assume that George navigated to a more detailed environment within Amazon just related to shovels 1726. Window 1724 illustrates this level in which the dynamic widget 1730 presents the option to give a virtual egift 1728 with a particular person who populates the To: field and the For: field is pre-populated with shovels. The system can also pre-populate an amount based on the average cost of a shovel and other options further tailoring the virtual egift. The giver selects a “purchase” field 1732 and/or “send an egift” field 1734 to send an egift. George is sending to Rachel a virtual egift with a scope limited to use for a shovel on Amazon.com. This is of course because of the context in which widget 1730 is presented based on the George's current search and/or other context information. George clicks on the space item of the shovel portion and browses to the interface shown in FIG. 17D.

FIG. 17D illustrates yet a more specific context of searching within Amazon in which a specific item such as a spade is identified 1738. Window 1736 shows review information and specific cost of $9.75 plus $2 shipping. Here, specific “One Click” options are presented such as “Send a Spade to Rachel” with button 1740. Another option is to send a virtual egift to Rachel with button 1742. These specific “One Click” purchasing options can be presented in an environment where the various recipient and giver information is previously known. Widget 1746 also illustrates the various options of selecting who to send the virtual egift to such as “To: Rachel” and “For: Spade” prepopulated with the particular spade that is being viewed. The system can also pre-populate an amount of $11.75 based on the price of the spade plus the estimated or actual shipping amount and provide various other buttons such as an Options button, Edit button, and a Preview button. The giver can then purchase a virtual egift for the recipient manually, via a “one click” purchase, or purchase the spade itself and send it to the recipient.

As can be seen in the various modifications to the egift options presented as the giver George navigates through a merchant website in FIGS. 17A-17D above, one aspect of this disclosure enables a dynamically modifiable scope when presenting an opportunity for a giver to decide whether to give a virtual egift to a recipient. The policy that would govern the redemption of such a virtual egift given by George in the above example is dynamically changing based on the currently viewed web page. The system retrieved data from what is currently being viewed with respect to products, amounts, holidays (is it a Thanksgiving web page, Christmas, etc.?) the date, social networking data, etc., to dynamically predict and modify what policy would apply if the viewer were to create an egift at that time.

FIG. 18 illustrates an example method associated with the feature discussed above. In one variation, the system identifies a giver browsing a page of a merchant web site (1802). Then the system retrieves account information of the giver (1804) and analyzes content of the page (1806). External data such as social networking data, the date, location, purchasing history, etc. of the giver and of potential recipients can also be retrieved and analyzed. The system can display a list of egift options to the giver based on the content of the page. The egift options can include a physical egift for a recipient, purchasing an item for the recipient, and/or sending a egift associated with a payment mode of the recipient such that when the recipient uses the payment mode to make a purchase, a egift amount is applied to the purchase (1808). The system can optionally update the list of egift options as the giver navigates to different pages of the merchant web site based on content of the different pages (1810). In a “one click” scenario, the policies, recipients, and so forth can dynamically change from page to page. On one page in which a stereo is being viewed, the system may present “George, give a $50 egift to your dad for Amazon.com to buy this stereo for his birthday next week.” George could one-click the interaction and the transaction is complete. As George browses to another page with a book about the Civil War, data may be used to present another egift option: “George, you can, with one click, purchase this Civil War book for John who loves history and has a birthday in two weeks.” Clicking on this option may present a egift for John to purchase the book or may just purchase and send the book to John.

In another variation, the system receives information associated with the context of an internet search for an item. The system further utilizes the context for populating a virtual egift interface for the giver. The system next receives selection information from the giver associated with generating a virtual egift of having a scope. Finally, the system manages the redemption of the virtual egift according to the scope such that the recipient can redeem the virtual egift using a standard payment mechanism. In this manner, the system can intelligently populate and transition between what to offer the giver as they navigate from more general descriptions of goods and services to specific categories of goods and services down to specific items. This dynamically modifiable presentation of a potential virtual egift will simplify and reduce the number or clicks necessary for a giver to commit to giving a virtual egift to a recipient.

One example of the narrowing of the potential fields within a virtual egift widget for a giver can be illustrated in the differences between FIGS. 17B and 17C. For example, the To: field in the widget 1718 of FIG. 17B does not show a prepopulated name given the context of the Amazon garden page 1714. The interface can include a prediction for the giver to send a card to Dad via the “one click” button 1722. The card would cover the scope identified in widget 1718, i.e. the card can be limited to use for garden items at Amazon and would be for $70. However, note that in FIG. 17C, the To: field in the widget 1730 is pre-populated with the name George. If the context information, which in this case is the Amazon shovels page, can provide a sufficient indicator of the likely desired recipient of that item or items or that category of items, then that information can prepopulate with widget for presenting the virtual egift structured to the giver.

Predictive Virtual Egifts

With respect to predictive uses of virtual egifts, FIG. 19 illustrates a system 1900 that can be used for a predictive approach of presenting an interface for a giver of a virtual egift. Online presence block 1902 represents an interface to the giver 1901 and what that interface presents to the giver. Specifically, with respect to predictive virtual egifts, the interface 1902 can present to the giver 1901 certain predictions about what types of virtual egifts the giver 1901 is likely to give. The system can tap in to and process various pieces of information in order to arrive at those predictions. For example, a recipient profile 1904 can be used for various recipients that are known to receive egifts or virtual egifts from the giver 1901. A giver profile 1906 can include information about the giver's previous habits, own purchases, and so forth. The system can analyze social networking data 1910 or other personal data sources to identify such information as birthdays, habits, preferences, location-based information, and activities of the giver 1901 as well as various levels information about friends, family and associates. For example, through the social network data, the control engine 1908 and/or the online presence information 1902 can retrieve birthdays of the giver's closest friends and family. This social networking data can be very valuable when predicting what virtual egifts the giver desires to give. The giver history 1912, the recipient history 1914 and a friend wish list 1916 can also communicate with one or more of the online presence 1902 or the control engine 1908 to provide additional information that the control engine 1908 can use when predicting virtual egift information. The control engine 1908 can utilize all or part of the various information, optionally assign weights to the various information, and combine it together to arrive at a prediction at any given time and based on any particular online presence information for the giver 1901 regarding what kinds of virtual egifts the giver desires to or should give.

FIG. 20 illustrates a example of this approach. Assume that window 2000 is the Neiman Marcus website and widget 2002 is presented that enables the giver to tap into and send a virtual egift for Neiman Marcus or some other merchant. A control engine can drive the behavior of the widget 2002 independent of the retailer web site. For example, the website 2000 is Neiman Marcus and the widget 2002 is offering egifts for other retailers. The goal would be to use the predictive egift mechanism to reduce the number of clicks necessary to actually have the giver purchase a virtual egift and send it for processing. Assume a giver viewing window 2000 clicks on the virtual egift button 2002, the system can present a predicted egift summary after the giver clicks, selects, hovers the cursor over, or provides other suitable input related to the virtual egift button. Given the context of information from one or more social networking data, online presence, giver history, recipient history and wish lists, and various profiles and so forth, FIG. 20 illustrates a predictive list of most likely recipients and that Dad 2006 should receive $100 2008 for Home Depot 2009. A Send button 2010 is presented such that if the giver decides to give the predicted egift, a single click sends off that egift to the right person with the right scope and for the right amount that Dad can redeem using his standard payment mechanism (Visa, American Express, MasterCard, etc.) at Home Depot. More information 2012 can be provided in case the giver desires to tailor the particular virtual egift in a more detailed way. Policies can be set, modified, and so forth for governing the redemption of the egift.

Other exemplary options shown include the potential that the giver would desire to give a egift to Rachel for $75. The system can provide other information 2014 such as why this is as predicted. For example, if Rachel is a friend and not a Father then it might be less likely that the giver would know why Rachel's name came up below the Father. Birthday information, wish list item information and historical information are presented 2016 that can help inform the giver regarding the particular person's position within the predictive list. Other suggestions in field 2018 are also available. The giver can hit Send 2010 to send a $75 virtual egift to Rachel. The giver can further expand the list to view more than the top persons on the predictive list and/or drill down for more information, secondary suggested egift amounts or merchants for a particular predicted person, and so forth.

FIG. 21 illustrates an exemplary method associated with the predictive process for virtual egifts. In a first aspect, the system retrieves a giving history of a giver (2102) and identifies a current context of the giver (2104). The current context can include multiple information sources, such as a current web page view, a time, a day, recently purchased gifts, recently received gifts, a browsing history, recent communications, scheduled calendar events, debt owed, and so forth. The system then generates a predictive list of egift suggestions based on at least one of the giving history, the current context, and other optional information (2106). A egift suggestion can include one or more of a recipient, a recipient history, a egift amount, and a egift merchant, for example. Then the system presents at least part of the predictive list of egift suggestions to the giver (2108). The predictive list can be based on a current activity and presented in the context of the current activity. Alternatively, the system can periodically (such as annually, monthly, weekly, or daily) analyze the giver's current context and send a notification, such as an email with interactive HTML components, of egift suggestions. The egift suggestions can include, for example, suggested amounts, recipients, and merchants. The system can provide a way for a giver to drill down and explore the reasons or motivation behind each suggestion. For example, the giver can click for more information on a suggestion for giving a $30 virtual egift to a potential recipient for her birthday. The system can display to the user that the previous year's virtual egift was $20 as a baseline, and explain that the suggested increase from $20 to $30 is based on inflation and on a personal or work relationship with the recipient that has grown closer over the last year. The system can also monitor the development of the giver's relationships with others, such as based on emails, social networking activity, life events, a change of school or workplace, and so forth, and suggest new virtual egifts that are not based on a previously sent egift.

In another variation, the system receives information from one or more sources including the social network data, giver history, recipient history, wish lists, giver profile and recipient profile. The system would process the information to identify a predicted recipient, dollar amount, context, scope, and/or other data associated with the virtual egift. The system presents to a giver according to a particular context, a predicted list associated with a potential recipient to whom the giver might give a virtual egift. Next, the system receives a selection from the giver of one or more recipients of a virtual egift according to the presented information. The system can then process the virtual egifts and transfer the indicated amount from the giver to the recipient upon the recipient purchasing an item under the constraints of the virtual egift using a standard payment mechanism. The system can present predictions via a dedicated egift prediction portal or as an add-on to an existing destination, such as msnbc.com, yahoo.com, or amazon.com. In some cases, the system can predict and/or suggest participation in a group egift. If the group egift is not yet established, the system can prompt the giver to create the group egift, perhaps based on a previously sent group egift as a template for the amount, potential givers, message, merchant, and so forth. Group egifts are discussed more fully below.

Virtual eGIFTS with Loyalty Cards

FIG. 22 illustrates another example use of the system 2200 at a point of sale 2202. A egift recipient pays for purchases using cash 2204, check, a payment card such as a Visa or debit card 2206 in conjunction with a club card 2208. The club card 2208 can make the recipient eligible for certain promotional discounts or savings. The virtual egift can be tied to the club card 2208 to identify transactions to which the system applies the egift. One example of such a club card or loyalty card is a Safeway club card in which the recipient receives discounts of items purchased at Safeway when they give the person at the register either the club card or a phone number which identifies them as a member of the club. Thus, the term “club card” does not require the recipient to be part of a club and is not limited to a physical card embodiment.

In this example, the egift server 2210 communicates with a credit card operator 2214 and a merchant server 2212 as well as hardware at a point of sale such that the virtual egift can be applied to a particular purchase independent of whether the recipient used cash, a club card or a payment card in the normal fashion. For example, assume $10 in a virtual egift has been presented to a recipient John. John goes to a point of sale but uses cash 2204 or a check to buy $10 worth of groceries. If the point of sale uses a club card information 2208 in order to process the transaction, the entry of the club card information can be communicated to a merchant server 2218 and/or a egift server 2210 such that the virtual egift amount can be applied to that purchase. The teller at the point of sale 2202 can simply inform the recipient that, as part of this transaction, a virtual egift was used to pay $10 and thus the recipient does not have to pay anything for that transaction. This can be accomplished because usually the club card information is provided during the transaction to arrive at the final amount (since the club member gets discounts). Therefore, the final amount can include the application of the $10 in a virtual egift.

In one example, the recipient completes the sale at a point of sale. When the teller receives the $10 in cash and identification of the club card, the sale can internally be completed but at the same time an additional transaction occurs in which the point of sale 2202 or the merchant server 2212 receives a credit of $10 from the egift server 2210. As the recipient is receiving a receipt at the point of sale 2202, the information that $10 has been credited for that transaction can already be provided. The teller can then essentially give the recipient their $10 cash back. In one scenario, the merchant prints a receipt including a message such as “Happy Birthday, Love Mom” to notify or remind the recipient of who is giving the virtual egift and to confirm that the virtual egift was successfully applied.

FIG. 23 illustrates an example method embodiment for processing a virtual egift in connection with a club card. In this example, the system identifies at a point of sale and in connection with a purchase, a payment mode and a loyalty card from a recipient as part of the purchase (2302). The system identifies a egift amount associated with at least one of the payment mode and the loyalty card (2304). The system applies the egift amount to the purchase (2306). The recipient can use the loyalty card with the merchant in the form of a separately scanned physical card, or a recipient-entered passcode, password, telephone number, or other information unique to the recipient. The system can intercept this transaction at the merchant or point of sale level because the recipient may pay with cash, check, EBT (e.g. food stamps), or other form of payment without an existing account, but the system can intercept these transactions at other levels if the recipient pays with a credit or debit card.

Upselling with Virtual Egifts

FIG. 24 illustrates another opportunity for accessorizing, upselling, or otherwise modifying a virtual egift based on various pieces of information that can be presented when the giver purchases the egift, but which normally cannot be presented in a standard physical egift scenario. The system presents exemplary window 2400 just following a giver's decision to purchase a $50 virtual egift. The information 2402 can say something like “You Have Chosen $50 for an Outback Steakhouse virtual egift”. The system can deduce from information such as the merchant, the amount, the recipient, a recipient event, a message from the giver to the recipient, that the giver intends the egift to be for dinner for two. The system can then determine that the average dinner for two at Outback Steakhouse is $56.50. The system can ask the giver if the giver wants to increase your virtual egift by $6.50 2404 to meet the average dinner for two price. In another variation, the system can round the suggested increase amount, based on the actual average price, to a next round number, such as the next whole dollar or the next five dollar increment. Of course, the giver is free to adjust the increase amount up or down and can decrease the amount if the giver feels the amount is too high. Button 2406 receives the OK to increase the egift for that amount. The window 2400 can also include additional information to guide the choice, such as average drink cost, dessert cost, tip amount, and so forth.

This interface is helpful because the giver of the egift may not know the average cost for a particular restaurant and still desire to purchase an entire meal for the recipient and a friend or spouse. In one variation, the system accesses a database that includes data such as average meal costs, previous egift purchases for such a merchant, and so forth, but the system can also directly poll the merchant to determine and/or confirm this or similar information. Any such information is contemplated as being used to adjust either up or down the suggested amount for a virtual egift. For example, the opposite may be true when the giver has chosen a $50 egift for dinner for two at McDonalds. The information 2402 can indicate that the average meal at McDonalds is $12 and actually suggest that the egift be reduced if the desire is to present a dinner for two at McDonalds. However, the virtual egift for $50 may be appropriate for dinner for six at McDonalds.

“Dinner and a Movie” eGIFTS

The disclosure now turns to a discussion of a “Dinner and a Movie” example embodiment. While the example presented herein is “Dinner and a Movie”, the same principles apply to virtually any scenario where the exact dollar value of the virtual egift is not known or indefinite until the time of the purchase. FIG. 25A illustrates another egift interface 2500 that differs in that no particular dollar amount is presented. This example illustrates a egift where the giver wants to buy dinner and a movie for two for Rachel for her 10th anniversary 2502 and a button 2504 to buy the egift for dinner and a movie without a specific amount. The system can associate a number of restrictions with this egift. The processing and/or establishment of a policy by the giver can provide an outside limit to the purchase such as $210, as well as other limitations such as location, time and so forth. In an optional variation of the interface 2500 illustrated in FIG. 25B, the system determines an estimated or actual average and/or maximum possible amount for the dinner and a movie for two and allows the giver to confirm 2504 these amounts. The interface 2500 illustrates an example estimated average cost for dinner and a movie of $89.20 and an example maximum cost of $210. The system can determine the maximum amount based on various information such as average price of restaurants around the recipient's location or restaurants the recipient frequently visits, the average cost of movies, the recipient's shopping habits, and other factors to arrive at the estimated average cost and/or a maximum cost of a virtual egift for dinner and a movie for two. Of course, this can vary depending on zip code, restaurants in the area, and so forth. The system can rely on a database of such merchant information, such as a menu, price list, and so forth, to be able to present the egift interface 2500.

The system can apply the virtual egift to a purchase of dinner and a movie and items such as parking or concessions such as popcorn, candy, or drinks that all occur within a span of five hours. The system can process money from the giver's account or a third-party account to the recipient's account after the process and/or purchases are complete. If the giver presents a virtual egift for dinner and a movie for two, and a the recipient goes out to dinner the next night but does not go to a movie, then the virtual egift does not refund or transfer money to the recipient's account. If the recipient goes to dinner several more times but then three weeks later goes to dinner and then a movie, the system can apply the egift amount because the policy associated with the virtual egift is that the dinner and movie must occur within 6 hours of each other. In such a timeline for a successful dinner and movie egift application, the recipient pays for dinner at 6:00 pm on a Friday, and purchases movie tickets at 7:00 pm the same day, and purchases popcorn, drinks, and candy at 7:15 pm the same day. Once the recipient fulfils the requirements, the recipient's debit or visa card that was used to make these purchases can be credited with the appropriate amount to pay for all of the dinner and a movie within the bounds set by the giver. In another example, the recipient pre-purchases the movie tickets the day before, so the actual purchase is not within the six hour window. The system can base a determination that the necessary requirements were filled based on other factors than the purchase time, such as the actual show time and date associated with the purchased tickets. This can be more important for sporting event tickets that people often purchase weeks or even months in advance.

The system can present appropriate notifications, such as email communications, to let the recipient know that the virtual egift has been redeemed and that the giver hopes they had a wonderful time at their dinner and a movie. This all becomes possible because of the use of a network based virtual egift in which the redemption is tied to the recipient's standard existing credit/debit card. Various triggers can be used in a policy to track the various purchase events and to ensure that their inter-relationships comply with the policy.

FIG. 26 illustrates a system 2600 for processing such a egift request from item or service with no definite amount. Block 2604 represents a user interface that receives from giver 2602 a egift request for such an item or service that has no definite amount at step 1. The request can be communicated to a server 2606. The server can then reach out and communicate with various vendors at steps 2 and 3, a first vendor 2608 and a second vendor 2610 as well as other vendors to receive estimated costs for the dinner, the movie, the bracelet, or any other item for purchase or service. Alternatively, the server 2604 performs a database lookup to estimate costs without communicating with the vendors 2606, 2608 directly. That maximum amount is communicated back to the giver 2606 in step 4. When the giver 2602 optionally confirms in step 5 that the egift is approved, server 2606 then accesses at step 6 the giver account 2614 to either withdraw money or reserve the maximum amount for such a virtual egift (which is $210 as shown in the example shown in FIG. 25B). Then, as is noted in the scenario above, when the recipient actually purchases the item or service, such as a dinner and a movie from the vendors 2606, 2608 via the recipient account 2612 at step 7, a final actual amount is identified is step 8 by the server. Step 8 also involves applying the actual amount from the held or reserved amounts from the giver account 2614 to the recipient's purchase. Step 9 involves releasing the remaining amount and step 10 optionally notifies the giver of the release.

In the example provided in FIG. 25B, assume that the estimated amount was $89.50. The maximum amount for the dinner and the movie was $210. According to FIG. 26, the system holds or reserves $210 from the giver account 2614. Assume that after the recipient actually went to a dinner and a movie, the actual cost was $110. From the giver's account 2614 and in accordance with the policies, the system applies $110 to the recipient account either to reimburse or to pay for the dinner and a movie according to a variety of methods. This leaves $100 as the remaining amount to be released back to the giver account 2614 into its general funds. The system can notify the giver 2612 of the release and of the amount that was actually used by the recipient for the dinner and a movie. Furthermore, the recipient can receive in association with the initial dinner and a movie virtual egift, a notification stating, “George has given you a virtual egift for your birthday for dinner and a movie. Redeem this egift by going to dinner and a movie within 5 hours of each other. Once you have completed that series of purchases using your Visa card, the entire cost for the dinner and a movie will be credited to your account. Happy Birthday.”

FIG. 27 illustrates an example method embodiment associated with the indefinite virtual egift. The system first receives, from a giver, a first identification of a recipient and a second identification of a gift object costing an indeterminate amount of money at a first time (2702). The system optionally determines an estimated maximum amount of money of the gift object (2704). The system can also optionally confirm with the giver that the estimated maximum amount of money is acceptable as a egift (2706). The system reserves the estimated maximum amount of money from a giver account (2708). The system identifies a recipient payment mode (2710). Upon the recipient using the recipient payment mode to make a purchase of the gift object at a second time that is later than the first time (2712), the system identifies an actual cost of the gift object (2714) and applies the actual cost of the gift object from the estimated maximum amount of money to the purchase (2716). The system can optionally release the remaining portion of the estimated maximum amount of money to the giver (2718).

In an alternate method embodiment, the system receives from a giver a virtual egift request for an item or a service with no definite amount. The server next optionally can retrieve information from various vendors and transmit to the giver a predicted amount of the cost for the item or service. The system can also optionally receive a confirmation from the giver for the estimated amount. The system next receives information that a recipient of the virtual egift has used a standard purchasing mechanism to buy the item or service. The system then identifies an actual amount used in the transaction and applies from the giver account an amount of money associated with the actual amount to the recipient account. The system finally releases any remaining amount to the giver account that was held or reserved as a maximum cost associated with the indefinite amount.

Intercepting Virtual eGIFT Transactions

FIG. 28 illustrates an example payment processing chain 2800. This chain 2800 is representative and can include more or less steps, including variations with multiple concurrent paths for different payment modes, such as a branch for processing credit cards and a branch for processing debit cards. The system for processing virtual egifts can intercept transactions at any of multiple locations in the chain 2800, depending on the type of virtual egift, the type of underlying purchase or transaction, the issuer of the virtual egift, and other factors. In this chain, a user 8002 presents a credit/debit card or other payment instrument at a point of sale 8004. The point of sale can be a brick and mortar retailer, such as a checkout cash register at Target, or a virtual storefront, such as Amazon.com or a mobile device store for downloading applications. The point of sale 8004 can first verify that the payment instrument is valid and has sufficient funds or credit to complete the transaction. To this end, the point of sale 8004 can communicate with a merchant/gateway 8006. The system can intercept payments at the point of sale 8004 level and/or the merchant/gateway 8006 level in order to process virtual egifts associated with club cards or loyalty cards, for example. The merchant/gateway 8006 can communicate with a bank 8008, and the bank 8008 can communicate with a credit card issuing bank 8010.

Either the bank 8008 or the credit card issuing bank 8010 confirms that credit is available and can reserve that credit for payment for the transaction or confirms that funds are available for the transaction and withdraws those funds from the user's account. Then the various entities communicate back through the chain to the point of sale 8004 to confirm that the user's payment device is valid and has sufficient funds or credit to complete the purchase. Then the point of sale can complete the purchase. The system can intercept these transactions at any stage in the chain and can intercept transactions at multiple stages. The system can intercept a transaction at a point of sale to apply part of the virtual egift associated with a loyalty card. The system can intercept the transaction at a merchant/gateway 8006 level to apply a main portion of the virtual egift amount, but can also intercept the same transaction at the credit card issuing bank 8010 level to apply a promotional bonus for using an American Express card.

As has been noted above as well, the system can analyze the recipient payment history for transactions that qualify under a egift policy. If the recipient has a egift for Olive Garden and another egift for any hardware store, the system may every Saturday or at any interval or triggered by any event, scan the appropriate payment history (which can span from the time the egift is given and even prior to giving the egift if instructed), and identify qualifying transactions. If the system determines that a purchase at a hardware store was made, then the egift for that purchase is processed and the egift amount of money is applied to that transaction. If two weeks later a purchase is made at the Olive Garden, that transaction will be detected in the transaction history and the policy for that egift will apply.

Generating and Displaying Egifts

FIG. 29A illustrates a layered view 2900 of an example configuration of a virtual egift 2902 according to some aspects. As illustrated in the layered view 2900, the virtual egift 2902 includes an image overlay 2904 and an image underlay 2910. The image overlay 2904 includes a separable flap 2906 for unwrapping the virtual egift 2902 by peeling or tearing off or unwrapping the image overlay 2904 to expose or visually enable the image underlay 2910. The separable flap 2906 can appear as a portion of the image overlay 2904 that is curled or unadhered to the image underlay 2910. The image overlay 2904 can also include information about the egift 2902, such as a description or comment, a label, instructions for using the separable flap 2906 to unwrap the virtual egift 2902 (e.g., by peeling or unwrapping the image overlay 2904) and view its contents provided by the image underlay 2910. Other example interface elements can include a link (e.g., to an account, a giver, an email, a contact, an object, a terms and conditions page, an instructions page, etc.), a button (e.g., an enter button to trigger an unwrapping event as described below, an accept button, a cancel button, a use button, an enable button, etc.), information (e.g., a description of the egift 2902 and/or the separable flap 2906, a name of the giver or merchant, an expiration date, a technical requirements, etc.), a symbol (e.g., a money symbol, a gift symbol, an open symbol, an unwrap or peel symbol, a trademark symbol, etc.), an image or animation, a note, etc.

The image overlay 2904 does not display the gift credit configured for the virtual egift 2902, or other information in the egift 2902, such as a merchant 2916 for the gift credit, instructions for use, etc. The image underlay 2910 contains the gift credit information 2914, as well as any other information pertaining to the virtual egift 2902, such as the merchant 2916, the giver 2918, and/or any other information about the virtual egift 2902. In some cases, the image underlay 2910 can include a label 2912, which can extend below the separable flap 2906 when in a curled, unadhered, or separated state, to indicate to the user to open or enter through the separable flap 2906 to unwrap the egift 2902. However, the entire image underlay 2910 is not visible to the user while the image overlay 2904 is not unwrapped and is instead visibly displayed to the user (e.g., via a screen or display on a device such as system 100 shown in FIG. 1), as the image overlay 2904 is configured to appear as a cover, top, and/or wrapping layer of the virtual egift 2902, and obscure, block, or hide the contents of the virtual egift 2902, including at least a portion of the image underlay 2910 and its associated contents. The image underlay 2910, and thus the associated egift information (2914, 2916, 2918) on the image underlay 2910, can become visible after a virtual unwrapping event removes the image overlay 2904 and exposes the image underlay 2910, as further described below. Thus, as long as the image overlay 2904 is displayed, prior to the virtual unwrapping event, the image underlay 2910 and its associated information (2914, 2916, 2918) will be hidden from the user.

To view or access the image underlay 2910 and its associated information (2914, 2916, 2918), a virtual unwrapping event can be triggered to remove the image overlay 2904 and expose the image underlay 2910. The virtual unwrapping event can graphically depict or simulate the unwrapping of the image overlay 2904, until the image underlay 2910 is left exposed and visible to the user. The virtual unwrapping event can be an animated simulation showing the image overlay 2904 being removed, peeled off, or unwrapped from the virtual egift 2902. From the user's perspective, the virtual unwrapping event can mimic the experience of unwrapping a gift to view or access the gift's contents, peeling off a label or sticker, tearing off a wrapping paper or covering, etc. Thus, when the virtual unwrapping event is initiated, the image overlay 2904 can begin to unwrap, peel off, or separate from the image underlay 2910 in a visual and/or animated way. The image underlay 2910 and its associated content will then become visible to the user.

The virtual unwrapping event can be triggered by an input or interaction with the separable flap 2906 and/or the virtual egift 2902. For example, the virtual unwrapping event can be triggered by an interaction with the separable flap 2906, which initiates the removing (e.g., peeling off, tearing off, unwrapping, etc.) of the image overlay 2904 from the virtual egift 2902. The separable flap 2906 can appear as an extended or unadhered portion of the image overlay 2904, a loose or perforated tab or element, etc., which visually represents or depicts an area that can be used to unwrap the virtual egift 2902 by removing the image overlay 2904 (e.g., peeling or tearing off the image overlay 2904, unwrapping the image overlay 2904, etc.) to expose the image underlay 2910 and its contents. In some cases, the separable flap 2906 can include a visually perforated line 2908 or area to indicate to the user that the separable flap 2906 is unadhered, folded, curled, loosened, or separated, up to the visually perforated line 2908, and signal to the user that the image overlay 2904 can be unwrapped or peeled off by folding, peeling, unwrapping, tearing, separating, removing, etc., the separable flap 2906 beyond the visually perforated line 2908 until the image overlay 2904 is removed and the image underlay 2910, or an adequate portion thereof, becomes exposed or visible to the user.

The input or interaction with the separable flap 2906 to initiate the virtual unwrapping event can include, without limitation, a selection of the separable flap 2906 (e.g., via a cursor, touchscreen, a command, etc.), a gesture representing a pulling or peeling of the separable flap 2906, clicking on the separable flap 2906, a scrolling or hovering action, a voice command, a selection of an input interface element configured to enable or trigger the digital unwrapping event, or any other input and interaction with the virtual egift 2902.

Once the virtual unwrapping event is initiated, the image overlay 2904 will be removed, unwrapped, peeled off, torn off, separated, etc., starting with the separable flap 2906. The unwrapping event can be dynamic or animated. On completion of the unwrapping event, the image underlay 2910 will be exposed and visible to the user. The image underlay 2910 can similarly be animated or interactive for the user. For example, as the image underlay 2910 becomes visible/exposed, the shape, size, color, characteristics, etc., of the image underlay 2910 can change (e.g., dynamically or in an animated fashion). To illustrate, the image underlay 2910 can spread across the screen or display as it becomes visible/exposed from the unwrapping event's removal of the image overlay 2904.

Once exposed or visible, the image underlay 2910 can display egift information for the user. The egift information can include a gift credit 2914 indicating the funds available for the egift 2902, the merchant 2916 for the gift credit 2914, the giver 2918, and any other information such as instructions, comments, terms, notes, etc. For example, the egift information in the image underlay 2910 shown in FIG. 29A specifies “Tom has sent you a gift of $50 for Service Store XYZ. The $50 refers to the gift credit 2914 for the egift 2902, which is also specified elsewhere in the image underlay 2910, the Service Store XYZ is the merchant 2916 associated with the egift 2902, and Tom is the giver 2918 of the egift 2902. The image underlay 2910 in this example also provides a note to “Use service to redeem”, where the service refers to services/purchases at the merchant 2916, Service Store XYZ. Other information presented in the image underlay 2910 can include, for example, other information or links to other information such as a egift balance, a purchasing history, a promotion, a set of terms, a payment account hosting the gift credit 2914, an expiration date, an account number, a egift code, contact information, etc.

The shape and style of the egift 2902 can vary and may be based on one or more factors, such as recipient preferences; giver preferences; merchant preferences; the type of egift; the amount of funds in the gift credit 2914; a egift, merchant, or vendor brand; the size or configuration of the display device (e.g., smart television, LCD desktop display, smartphone display, tablet computer, laptop computer, smart wearables, IoT (Internet of things) devices, game system, etc. For example, in FIG. 29A, the digital egift 2902 is shaped as a teardrop or guitar pick. However, other shapes and sizes, such as rectangles or virtual credit cards, triangles, virtual checks, virtual gift boxes, virtual bags, virtual cakes, virtual cans, etc., are also contemplated herein and illustrated below with reference to FIGS. 30, 31, and 32.

FIG. 29B illustrates an example view 2920 of the virtual egift 2902 prior to an unwrapping event. The virtual egift 2902 can be presented on a screen or display at a device, such as a laptop, a smartphone, a desktop computer, a tablet computer, a smartwatch, a television, a game system, smart glasses, an IoT device, etc. The virtual egift 2902 can be rendered on a user interface at the screen or display, a website or webpage, an application (e.g., a egift application, a merchant application, a bank application, a social network application, etc.), an email, a text message, a video, etc., or may be rendered as a standalone virtual object such as a standalone virtual card object.

The virtual egift 2902 in this example is shown prior to an unwrapping event, and displays the image overlay 2904, which includes a separable flap 2906 for unwrapping the image overlay 2904 to expose or display the image underlay 2910 of the virtual egift 2902, a virtual perforated line 2908 which represents a curled or folded boundary of the separable flap 2906, an unadhered boundary of the separable flap 2906, a start point for unwrapping or unadhering the image overlay 2904 though the separable flap 2906, etc. In some cases, the separable flap 2906 is visually shown partly curled, unadhered, unattached, and/or separated from the image underlay 2910, up to the virtual perforated line 2908 or boundary. In some configurations, the image overlay 2904 can also include information about the virtual egift 2902, such as a description or note, a label, a logo, etc.

A portion of the image underlay 2910 adjacent to the virtual perforated line 2908 can be visible due to the curled, unadhered, unattached and/or separated nature of the separable flap 2906. The portion of the image underlay 2910 visible to the user can indicate to the user that an under layer is disposed below the image overlay 2904, to inform the user that removal of the image overlay 2904 will allow the full image underlay 2910, and the egift contents, to be exposed or displayed for the user. The visible portion of the image underlay 2910 can also include a label 2912 instructing the user to enter or open the egift 2902 to access its contents. This can prompt the user to initiate an unwrapping event to remove the image overlay 2904 through the separable flap 2906 and access the contents in the image underlay 2910.

FIG. 29C illustrates a sequence diagram of an example unwrapping event. In this example, the diagram illustrates different unwrapping states 2930A, 2930B, 2930C of the virtual egift 2902 across time 2934. The unwrapping states 2930A, 2930B, 2930C are respectively shown at time 1 (2934A), time 2 (2934B), and time 3 (2934C).

At time 1 (2934A), the unwrapping state 2930A of the egift 2902 shows an unwrapping progress represented by the length 2932A of the visible portion of the image underlay 2910. The length 2932A spans from the edge of the visible portion of the image underlay 2910 and the virtual perforated line 2908 of the separable flap 2906. As the length 2932A increases, the unwrapping progress advances and the visible portion of the image underlay 2910 increases.

At time 2 (2934B), the unwrapping state 2930B of the egift 2902 shows an unwrapping progress represented by the length 2932B of the visible portion of the image underlay 2910. The length 2932B spans from the edge of the visible portion of the image underlay 2910 and the virtual perforated line 2908 of the separable flap 2906. As illustrated here, the length 2932B in the unwrapping state 2930B is greater than the length 2932A in the unwrapping state 2930A. Thus, the visible portion of the image underlay 2910 has increased, and a greater portion of the image underlay 2910 is now visible and unobstructed by the image overlay 2904.

At time 3 (2934C), the unwrapping state 2930C of the egift 2902 shows an unwrapping progress represented by the length 2932C of the visible portion of the image underlay 2910. The length 2932C spans from the edge of the visible portion of the image underlay 2910 and the virtual perforated line 2908 of the separable flap 2906. As illustrated here, the length 2932C in the unwrapping state 2930C is greater than the length 2932A in the unwrapping state 2930A and the length 2932B in the unwrapping state 2930B. Thus, the visible portion of the image underlay 2910 has increased at the unwrapping state 2930C, and a greater portion of the image underlay 2910 is now visible and unobstructed by the image overlay 2904. The visible portion of the image underlay 2910 at unwrapping state 2930C now displays the gift credit 2914, the merchant 2916, the giver 2918, and other information. At this stage (i.e., time 3 (2934C)), the egift 2902 is almost fully unwrapped.

FIG. 29D illustrates an unwrapped view 2940 of the virtual egift 2902 after an unwrapping event (e.g., 2930A, 2930B, 2930C). The unwrapped view 2940 shows the image underlay 2910 unobstructed by the image overlay 2904, which was removed by the unwrapping event. The image underlay 2910 in the unwrapped view 2940 displays the information in the egift 2902, such as the merchant 2916, gift credit 2914, giver 2918, and any other information. The unwrapped view 2940 of the egift 2902 can be displayed at any screen or display as previously explained. The egift 2902 displayed in the unwrapped view 2940 can be animated for the user, as further described below. For example, the egift 2902 can be maximized or enlarged on the screen or display, or may be presented in a different shape and/or color.

FIG. 29E illustrates a modified view 2950 of the egift 2902 during and after the unwrapping of the egift 2902 (i.e., the unwrapping of the image overlay 2904). In this example, the modified view 2950 is presented at a computing device 100, as shown in FIG. 1, on a screen or display (170) of the computing device 100. As illustrated, the computing device 100 includes an input component 190 for interacting with the egift 2902 and an audio output component 170 for receiving audio information from the computing device 100, such as instructions for the egift 2902, special sound effects for the unwrapping, audio notes or comments, etc.

In this example, the egift 2902 is first shown in a wrapped state 2952, with the image overlay 2904 over a partly obstructed image underlay 2910A. At step 1 (2952), the separable flap 2906A with the virtual perforated line 2908A is moved to peel, unwrap, or remove the image overlay 2904. The separable flap 2906B and virtual perforated line 2908B illustrates the location or position of the separable flap 2906A and virtual perforated line 2908A after being moved to unwrap the image overlay 2904. At that point, a greater portion of the image underlay is exposed.

At step 2 (2954), the image overlay 2904 is completely peeled, unwrapped, separated, removed, etc., to expose the underlay image 2910B. At this point, the egift 2902 is in an unwrapped state 2954. The underlay image 2910B after step 2 (2954) is fully unobstructed by the image overlay 2904. The contents of the unobstructed image underlay 2910B displays the egift information, such as the merchant 2916, the giver 2918, the gift credit 214, etc. The unobstructed image underlay 2910B can spread to fill the screen (170) or a portion of the screen. In this example, the unobstructed image underlay 2910B is shown in the process of being maximized after the unwrapping of the image overlay 2904. The unobstructed image underlay 2910B can be maximized automatically after the unwrapping of the egift to prominently display the unobstructed image underlay 2910B and its associated information, or can be maximized manually by the user.

In some cases, the maximizing of the unobstructed image underlay 2910B can be animated for the user. Moreover, in some cases, the shape, color, size, transition effect, behavior, or configuration of the unobstructed image underlay 2910B can vary based on one or more factors, such as user preferences; a screen or display size, resolution, or capabilities; a giver's preferences; a merchant's preferences; a type of egift 2902; a type of device used to access the egift 2902 (e.g., a smartphone, a smartwatch, a television, a laptop, a tablet computer, etc.; a current activity of the user at the computing device 100; a type of application or interface used to display the unobstructed image underlay 2910B; a type of operating system (OS) at the computing device 100; a configuration of a webpage or interface hosting/presenting the unobstructed image underlay 2910B; etc.

FIG. 30 illustrates an example configuration of a virtual egift 3002 and example views 3000, 3020 of the virtual egift 3002. In this example, the virtual egift 3002 has a different shape than the virtual egift 2902 shown in FIGS. 29A-E. Namely, in this example, the virtual egift 3002 appears in the common, rectangular shape of most physical gift cards.

Wrapped view 3000 illustrates the virtual egift 3002 wrapped or covered with an image overlay 3004. The virtual egift 3002 in the wrapped view 3000 includes an image overlay 3004, a separable flap 3006 representing an area to remove (peel, unwrap, unadhered, separate, etc.) the image overlay 3004 as part of an unwrapping process, and a virtual perforated line 3008 which represents a boundary between a bound or adhered portion of the separable flap 3006 and an unbound, unadhered, curled, separated, or loosened portion of the separable flap 3006. The virtual egift 3002 in the wrapped view 3000 also illustrates a visible portion of the image underlay 3010. The visible portion depends on the unadhered portion of the separable flap 3006: the further unwrapped the image overlay 3004 is, the larger the portion of the image underlay 3010 that is visible to the user.

In this example, the visible portion of the image underlay 3010 extends from the top-left edge of the virtual egift 3002 to the virtual perforated line 3008, which represents the space on the image underlay 3010 that is open or uncovered by the image overlay 3004, including the separable flap 3006. The open or uncovered portion of the image underlay 3010 can be open or uncovered due to the separable flap 3006 being partially curled, unadhered, separated, peeled, etc., thus leaving a portion of the image underlay 3010 uncovered by the image overlay 3004.

After an unwrapping event 3012 in which the separable flap 3006 unwraps, peels, separates, removes, or unadheres the image overlay 3004 from the virtual egift 3002, at unwrapped view 3020, the egift 3002 is shown without the image overlay 3004. The unwrapped view 3020 depicts the image underlay 3010 unobstructed by the image overlay 3004. Accordingly, the image underlay 3010 and its associated content are visible to the user in the unwrapped view 3020.

In the unwrapped view 3020, the egift 3002 displays the gift credit 3014, the merchant 316, and the giver 318. Other information can also be displayed in the image underlay 3010, such as egift instructions, notes, comments, links, merchant information, terms, account information, logos, etc.

FIG. 31 illustrates another example configuration of a digital egift 3102. In this example, wrapped view 3100 shows the virtual egift 3102 in a wrapped state. Here, the virtual egift 3102 resembles a rolled paper and depicts an image overlay 3106 representing an outer layer or side of the egift 3102, and a protruding section 3104 which provides an opening or area to unroll the rolled egift 3102.

View 3110 illustrates the egift 3102 in a flattened or unrolled state after an unrolling event 3108 which unrolls the rolled egift 3102 from view 3100, to stretch and/or open the rolled egift 3102 and expose its inner contents. As illustrated in the unrolled view 3110 of the egift 3102, an image underlay 3112 depicts the inner contents of the egift 3102. In this example, the image underlay 3112 displays the gift credit 3114 of the egift, the merchant 3116, the giver 3118, and any other information. The image underlay 3112 can be exposed by the unrolling event 3108, which can be triggered by an input or an interaction with the protruding section 3104 of the egift 3102 in view 3100. The unrolling event 3108 can be visually executed on a device in an animated or moving fashion. The image underlay 3112 displayed after the unrolling event 3108 can similarly be presented with animation or other visual or audio effects. For example, the image underlay 3112 can be revealed in response to the unrolling event 3108 and scaled or maximized in a dynamic, static, or animated fashion, for example.

FIG. 32 illustrates another example configuration of a virtual egift, including a wrapped view 3200 of the egift and an unwrapped view 3210 of the egift. In the wrapped view 3200, the egift 3202 includes an image overlay 3204 which represents a gift wrapping or cover. The image overlay 3204 prevents the user from viewing or accessing the contents of the egift 3202 without first unwrapping the egift 3202 to remove the image overlay 3204.

The image overlay 3204 includes a graphical ribbon 3206 which represents a ribbon for wrapping gifts. The ribbon 3206 can include a bow 3206A and/or a protruding tab 3206B for removing the ribbon 3260 and the image overlay 3204 to unwrap the egift 3202. The bow 3206A can facilitate the unwrapping of the egift 3202. For example, an input or interaction for removing the bow 3206A or pulling on an end of the bow 3206A can trigger an unwrapping event 3208 to unwrap the egift 3202 and view the egift contents as shown in the unwrapped view 3210. The protruding tab 3206B can similarly facilitate the unwrapping of the egift 3202. For example, an input or interaction for pulling, peeling, or tearing the protruding tab 3206B from the egift 3202 can initiate or trigger the unwrapping event 3208 and transition from the wrapped view 3200 to the unwrapped view 3210 where the contents of the egift 3202 are visible and accessible for the user. The pulling, peeling, or tearing of the protruding tab 3206B can cause the ribbon 3206 to be removed and the wrapping of the egift 3202, represented by the image overlay 3204, to be disassembled, removed, or unwrapped.

After the unwrapping event 3208, which can be initiated or triggered via the bow 3206A and/or the protruding tab 3206B as previously explained, the egift 3202 transitions to the unwrapped view 3210, which depicts the contents of the egift 3202 as displayed in an underlay image 3212. The underlay image 3212 in the unwrapped view 3210 can depict, for example, the gift credit 3214 of the egift 3202, the merchant 3216, the giver 3218, etc. In some cases, the underlay image 3212 can display other information and/or objects, such as use instructions, egift or merchant terms, notes from the giver 3218 and/or the merchant 3216, rules and/or conditions, information about a vendor of the egift 3202 and/or the merchant 3216, a link to external information such as a webpage or an account (e.g., payment account, website or service account, etc.), a balance associated with the egift 3202, an object to initiate actions such as a drop-down menu or an input field to use or modify the egift 3202, an interface element to initiate a communication session (e.g., via electronic mail or text) or send/store the egift 3202 to a specified destination, an element to transfer or add funds, etc.

FIG. 33 illustrates an example method for generating and using a virtual egift (e.g., 2902). For the sake of clarity, the steps will be described with reference to a computing system 100, as shown in FIG. 1, configured to practice the steps and operations in the method.

At block 3302, the computing system 100 receives an identification of a merchant (e.g., merchant 2916) selected by a giver (e.g., giver 2918) of a gift credit (e.g., 2914) for an egift (2902). The giver of the gift credit has a giver payment account (e.g., a bank account, a credit/debit account, a digital currency account, etc.), and a recipient of the gift credit has a recipient payment account (e.g., a bank account, a credit/debit account, a digital currency account, etc.). In some cases, the giver can withdraw the gift credit for the egift from the giver payment account, and the gift credit associated with the egift can be deposited to the recipient payment account. The recipient can thus use the recipient payment account to make a purchase with the merchant. The gift credit used in the purchase can be applied from the recipient payment account based on the gift credit deposited into the recipient payment account based on the egift provided to the recipient.

At block 3304, the computing system 100 can associate a policy with the gift credit. The policy can be at least in part defined based on the merchant. For example, the policy can provide that the gift credit can only be used with the merchant or applied to purchases with the merchant. In some cases, the policy can provide other parameters or restrictions. For example, the policy can define an expiration period after which the gift credit expires, a limit on the frequency or amount of purchases with the gift credit, transferring rules, usage limitations, currency requirements or restrictions, etc.

At block 3306, the computing system 100 generates a digital egift for the gift credit, including an image underlay (e.g., 2910) identifying the gift credit and an image overlay (e.g., 2904) which hides, covers, or conceals the image underlay and the gift credit identified in the image underlay. The image overlay can include a separable flap (e.g., 2906) having at least a portion that appears as being unadhered to the image underlay. The separable flap can represent a point or place for unwrapping the egift by removing or peeling the image overlay. In some examples, the separable flap can be configured to trigger, in response to an input associated with the separable flap, an animated unwrapping effect that removes the image overlay to reveal the image underlay identifying the gift credit. The input can be a selection, a gesture, a command, etc., which causes pulling, peeling, tearing, or unwrapping of the image overlay through the separable flap. For example, the separable flap can be clickable or selectable. A user can select the separable flap and initiate a pulling gesture (e.g., via a cursor or touchscreen interaction) that creates a pulling or peeling effect on the separable flap which results in the separable flap being peeled, removed, unadhered, unwrapped, removed, curled, rolled, etc., causing the animated unwrapping effect as the separable flap is peeled, removed, unadhered, unwrapped, removed, curled, rolled, etc.

At block 3308, the computing system 100 presents the image overlay hiding the image underlay. The image overlay can represent or depict the outer or surface portion of the egift, or an outer wrapping layer over the egift. The image overlay will not display the contents of the egift and will prevent the image underlay and its contents from being visible to the user, at least until the image overlay is at least partly removed by an unwrapping event. In some cases, the image overlay is configured as an outer layer of the egift and the image underlay is configured as an inner layer of the egift. Thus, the egift in this example has a layered configuration including an inner and outer layer, respectively represented by the image underlay and the image overlay. In this example, the outer layer of the egift (i.e., the image overlay) will conceal, cover, or otherwise obstruct the inner layer of the egift; namely, the image underlay and its associated contents. Accordingly, in this example, removal of the image overlay (at least partly) is necessary to reveal the image underlay and its associated contents (i.e., the egift contents).

In other configurations, the egift may not be designed with a layered structure. In other words, the egift may not include layers of content, such as an inner image layer (e.g., the image underlay) and an outer image layer (e.g., the image overlay). Instead, the egift may be configured as a single layer or a flat object. Each view or state of the egift can be depicted by a single image corresponding to the state or view of the egift, or a flattened file with one or more images or graphical elements corresponding to the state or view of the egift. For example, when wrapped, the egift can be depicted by a single image, such as an image overlay, which represents or illustrates a wrapped egift. This single image can depict the outer surface of the wrapped egift, a separable flap in the outer surface of the wrapped egift, and an area visible under the separable flap or extending from a visually curled, unattached/unadhered, or separated portion of the separable flap. Since the separable flap, or a portion of the separable flab, can appear as being visually curled or otherwise unattached/unadhered or separated from the rest of the egift wrapping (e.g., the outer surface), any area within the egift and below the visually curled, unattached/unadhered, or separated portion of the separable flap (e.g., the underlay or inner layer) can appear as a sublayer under the separable flap and wrapping. This visual curling, unattachment/unadherence, or separation effect of the separable flap can expose an area that would otherwise be covered by the wrapping or separable flap, creating an illusion that an inside of the egift being exposed by a partial unwrapping of the wrapped egift.

In this example, if the user then triggers an unwrapping event for unwrapping the egift to expose the inside contents (e.g., the image underlay) of the egift, the image depicting the wrapped egift can transition to a second image (e.g., the image underlay) that depicts the unwrapped egift, including the contents of the egift. In other words, the image depicting the wrapped egift can be replaced with another image depicting the unwrapped egift and its contents. Each view of the egift (e.g., the wrapped egift view and the unwrapped egift view) can each be depicted through a single image that is replaced when the egift transitions from one view (e.g., wrapped view) to another (e.g., unwrapped view). In some cases, the transition from the wrapped view to the unwrapped view can be animated using the image depicting the wrapped egift and the image depicting the unwrapped image. Other images can also be implemented as part of the visual unwrapping effect for different animated effects. For example, a plurality of images or frames can be implemented to depict various states of the egift through the unwrapping process, starting with the fully-wrapped egift and ending with the unwrapped egift. The plurality of images or frames can be displayed in a particular sequence and stitched together by software or scripts to generate an animation or movie-like visual effect. The peeling, tearing, separating, or unwrapping of the separable flap can similarly be animated using one or more images or frames. In some cases, scripts or code can be used to order various images or frames in a particular sequence and display the various images or frames according to the particular sequence and specific timing parameters to create an animated unwrapping effect.

At block 3310, in response to receiving an input associated with the separable flap on the image overlay, the computing system 100 generates the animated unwrapping effect to remove the image overlay and reveal the image underlay. The animated unwrapping effect creates an illusion perceived by users as the unwrapping of a wrapped egift. This animated unwrapping effect can be triggered by the input associated with the separable flap. The input can be a gesture or interaction with the separable flap, the egift, and/or an interface element displayed on the computing system 100. For example, the input can be a click or touch-based selection of the separable flap, a touch swipe gesturing peeling of the separable flap, a drag and drop operation which drags a selectable portion of the separable flap towards an opposite edge of the egift and drops the selectable portion on the opposite edge or a location within a distance of the opposite edge, a move gesture or operation with an input object or device (e.g., a cursor, a touch screen, a mouse, a keyboard, etc.) which simulates the grabbing and/or peeling of the separable flap, a command (e.g., a voice command, a text command, etc.), or any other gesture or interaction configured to initiate an unwrapping event which triggers the unwrapping effect or animation.

At block 3312, the computing system 100 presents the image underlay and the gift credit. The image underlay can depict the egift in an unwrapped state. For example, the image underlay can depict the inside and contents of the egift. The computing system 100 can present the image underlay and gift credit after the animated unwrapping effect. Thus, the animated unwrapping effect can culminate in the egift and its contents being displayed in an unwrapped or opened state which allows the user to view and access the egift contents, including the gift credit configured for the egift. The image underlay can also present other pertinent information, such as a merchant associated with the gift credit, instructions for using the gift credit, terms and conditions associated with the egift, an indication of the giver of the gift credit, an indication of a recipient payment account where the gift credit has been deposited for use with the merchant, one or more links to other content such as a merchant website or a payment account, an indication of a balance of funds, any restrictions imposed on the usage of the egift such as timing or transferability restrictions, input objects or fields for initiating a specific function such as transferring the egift/credit or sending a note to the giver, etc.

In some cases, the computing system 100 can present the image underlay representing the unwrapped egift in a particular format or interface. For example, the computing system 100 can present the image underlay in a maximized format spreading across the screen on the computing system 100. In other examples, the computing system 100 can present the image underlay within a frame, window, page (e.g., webpage), or interface which may constrain or dictate the shape and/or size of the image underlay presented. For example, the computing system 100 can present the image underlay within an email, a frame in a webpage, a window in an interface, etc.

In some cases, the user can select the presented image underlay or an interface element to modify the presentation of the image underlay. To illustrate, if the computing system 100 presents the image underlay representing the unwrapped egift within an email, the user can select the presented image underlay to cause the computing system 100 to zoom in or present the image underlay in a separate window, interface or application. For example, when the user selects the image underlay from the email or a webpage, the computing system 100 can display the image underlay in a separate window, application or interface, such as an image viewing application or editor, outside of the email or webpage where the image underlay was initially presented.

Like the transitioning from the wrapped egift view to the unwrapped egift view, the presentation of the image underlay representing the unwrapped egift can be animated or adjusted to create particular visual effects. For example, as the animated unwrapping effect transitions to the unwrapping state depicted by the image underlay, the computing system 100 can adjust the size of the image underlay progressively or in an animated fashion until the image underlay reaches a particular size or limit. To illustrate, as the wrapping is removed and the image underlay begins to appear on the display, the animation can continue to spread or grow the unwrapped egift (i.e., the image underlay) until it is maximized on the screen or until it reaches a particular size or limit.

For example, the unwrapping of the egift can be animated to give the illusion of the egift expanding when the wrapping is removed, as if the egift was being contained or limited in size by the wrapping. Once the wrapping is removed as part of the unwrapping, the egift can expand, pop out, or explode into its unwrapped state depicted by the image underlay. Other effects or animations, sizes, formats, and appearances are also contemplated herein, such as movement animations/effects, color changes or transitions, font size changes or animations, audio effects, etc.

FIG. 34 illustrates an exemplary user interface 3400 for requesting a reverse virtual egift. The scenario in which FIG. 34 will be discussed is a group of three friends who go out to dinner together, each order food and drinks, and at the end receive a bill or check for the combined amount, including a tip, of $53. The approach described and the user interface depicted in FIG. 34 provide a way to avoid the friends having to remember to bring cash, perform mathematical calculations to determine their share, or pay using three separate credit cards. One of the friends, Bob Jones, opens a reverse virtual egift application on his smart phone or other mobile device, which displays the user interface 3400. The reverse egift application provides an easy way for Bob to pay for the dinner and arrange for his friends to reimburse Bob for their portions.

Bob logs in and the device retrieves Bob's credentials 3402 associated with at least one payment account 3404, in this case a MasterCard credit card. Then Bob can select multiple givers 3406, 3408 and enter the amount that each owes for the dinner bill. Alternatively, Bob can use the mobile device to capture an image of the receipt, identify each item on the bill, and assign each item on the bill to one or more individuals. The system can identify accounts associated with each of the givers that include or have access to payment accounts for the givers, such as bank accounts, credit card accounts, debit card accounts, and so forth. Bob can also add other givers 3410. The interface 3400 can also display the total remaining on the bill 3412 that may or may not correspond to Bob's share of the bill. Bob can then submit the reverse virtual egift and the system notifies Giver 1 and Giver 2 of their proposed share of the bill, such as via text message or email, such as “You and Bob had dinner together at TGI Friday's. Bob is requesting that you pay $15 as your share of the bill.” The givers can confirm the proposal, add more money to the total, or otherwise interact with the notification to revise the amount. Upon receiving the confirmations from the givers, the system debits the respective amounts of money from each giver and credits those amounts of money to Bob's account as a reimbursement for paying the entire dinner bill.

In another concrete example, having individual payment cards registered makes sharing the cost of a meal easy. Assume Rachel, George, Grant and Geoff are at dinner and it is time to pay for the bill. Via a hand held device an application can be initiated for them to help determine how to share the bill. Rachel is going to use her credit card to pay. Upon initiation, Rachel can login or enter her name, look at the receipt, and do several things. The application can enable her to enter the total amount (including tax or have the tax calculated). The tip amount can be suggested, included automatically or manually. The tip may be automatically included on the receipt. All options can be presented. Rachel can look at the times she purchased and enter that amount for her portion. Often people will not want to the exact math but will want to enter an amount that is close. If Rachel's meal was $14.75 and she purchased an appetizer for $3.90, she may just enter in $19 as her part of the meal. The application can also present an option for her to add a portion of the tip by an exact amount or by a percentage of her portion. A suggested amount can be provided.

Therefore, for each person at the meal, a user interact enables the user to enter their amount, and get a tip amount, if any, into the system and associated with that person such that a final amount is arrived at. Next, George, Grant and Geoff enter in the amounts for their meals in the same manner. This may be done on the same handheld device or their own handheld devices. Their participation in this group dinner may be pre-populated or identified based on location-based information associated with their hand held devices. Rachel may be able to login in using whatever mechanism is available or known to login. Once Rachel enters her amount, the system may know via social networking plus location based data, or based on any other data available, that George, Grant and Geoff are in the group. When Rachel hands her device to George, he may only need to click on his name (or not), and enter in the amount of his meal with the variations on how to arrive at the tip. Each person interacts in the same manner with the device. Once everyone has entered in their data, a summary can be provided of the total amount, including tip, and tax information if necessary. This can provide a brief check for someone reviewing the bill that they have enough to cover the entire bill. Additions and modifications can easily be made. For example, if George realized he missed an appetizer and the overall bill is short, he can click on button to modify his amount. If the tip amount is way above an appropriate amount, the application can be used to reduce the tip by $5.00 and distribute that savings across the group. Each user is logged in or identified to the system such that each respective amount is associated with the appropriate person. The application can include a calculator option for people to be more exact in adding their portion of the bill.

Given that each person is in the system, the various credit/debit card accounts are known. The system can then confirm a payment plan for the group. Rachel then simply pays with her credit/debit card. Everyone group member's payment mechanisms is available and the respective amounts are retrieved from each giver account and associated with the transaction made by Rachel such that she is reimbursed. Rachel does not even need to be identified in the application as the one who will be making the payment. A policy can apply under the application for each particular such that when the group is identified with the respective member amounts, the group activity is monitored. For example, after all the data is entered, Rachel may have left her credit card at home. The application knows the group, knows the amount, and if George then pays the bill (rather than Rachel), the system can automatically turn Rachel into a giver and George the recipient. Indeed, in one aspect, no person needs to be identified as the giver. Each person only needs to enter their respective amount and then one in the group will pay. One or more in the group could pay as well and the system could work out the appropriate payments to each payer such that the right reimbursement is made to the correct respective payer.

Variations can easily exist in this context. Sometimes people treat someone for dinner since it is their birthday. The system can enable the group to each enter their amount of their meal, and then a total amount on the bill. Assume that it is Geoff's birthday and he does not enter an amount. Once everyone's amount is entered, and the total bill amount is entered as well, the system can determine the difference of what is left to pay (Geoff's dinner/tip/tax) and equally distribute that amount to the payers such that they each share in the cost of Geoff's meal. Then the appropriate amounts from the givers and paid to the recipient who uses their credit/debit card at the restaurant to pay for the meal. As noted above, the above functionality can be achieved using a single handheld device (or desktop or any other device) or may be accomplished via individual user hand held devices in which each user just starts up the application on respective devices, logs in, and enters their own data and confirms. Timing data (different members in the group each accessing the application at the same time or generally the same time), location-based data (each member of the group with their own device is determined to be in close proximity when accessing the application), social networking data (each member of the group works together or are friends on a social networking site), manually entered data (Rachel selects the others in the group from a list or enters their names or identification data to organize the group for the dinner payment), and/or any other received data or methods can be used to identify a group of people who are going to be associated with a payment transaction. Thus, the system can disambiguate between multiple tables of patrons at a restaurant where people may be accessing the system. In this scenario, George may be the first to enter his data. With the social networking, location based data, etc. Grant can then enter his data, and Geoff and Rachel enter their respective data. The system can present the final listing of the group to one or more people entering the data. Thus, Geoff or Rachel may have predictive or presented a definition of the group that they can confirm via one click. Corrections can be made or a top N groups can be presented from which they can choose the definition of the group. No specific buyer of the meal (or object, service, etc.) need be identified.

FIG. 35 illustrates a method embodiment of this approach. The system receives amount information from each person in a group of people who are going to be associated with a payment transaction (3520). The system associates each member of the group with a respective payment account or payment mechanism (3522). The system receives data that one person in the group paid via their payment mechanism (3524). The system then applies a respective amount of money from each person's payment account in the group to the one person who paid (other than the paying member) (3526). All the variations discussed above apply, such as dealing with tax and tip and various ways of prepopulating members of the group, or predicting members of the group. For example, the system may know that it is grandma's birthday and predict that the three children will each be there and want to share in the payment of the meal or a gift. This group payment option applies to any purchase transaction and not just meals. The application can be varied based on the type of transaction. For example, the users may begin the application and choose a meal (in which case the tax and tip options are presented for handling those additional items) or it may be a purchase of a car or a bike or gift that is to be shared. There are many mechanisms which can be applied to organize a group around any payment transaction. This approach can make a sometimes socially awkward experience of how to divide up a bill more convenient and easy to manage.

Various graphical presentations can be provided which demonstrate, for example, how much of the bill each person is paying in a pie chart or graph. Policies can be applied for each person in the group. For example, Grant in the above discussion, may want his payment applied in 15 days which is after his next paycheck is received. Such individual options can be provided which each user interaction or set in advance as they are managing their payment.

This principle can be applied to other non-dinner variations, such as arranging and paying for flowers at a funeral. An organizer can set up an open reverse egift for flowers for the funeral. As givers commit funds to the flowers, the amount of funds available for the flower grows. In the end, the system can determine, based on various package costs and the total available funds, which package of flowers is the best fit. For example, if the givers have committed $65 dollars total, the system can select a $59 floral package for the funeral. Alternatively, the system can determine that a $75 floral package is a better fit and send a request to all or part of the givers and request an additional contribution of $10 to reach the $75 for the next higher level floral package. Alternatively, the system can purchase the $59 floral package and distribute the remaining funds, $6, to one or more giver.

Embodiments within the scope of the present disclosure may also include tangible and/or non-transitory computer-readable storage media for carrying or having computer-executable instructions or data structures stored thereon. Such non-transitory computer-readable storage media can be any available media that can be accessed by a general purpose or special purpose computer, including the functional design of any special purpose processor as discussed above. By way of example, and not limitation, such non-transitory computer-readable media can include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code means in the form of computer-executable instructions, data structures, or processor chip design. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or combination thereof) to a computer, the computer properly views the connection as a computer-readable medium. Thus, any such connection is properly termed a computer-readable medium. Combinations of the above should also be included within the scope of the computer-readable media.

Computer-executable instructions include, for example, instructions and data that cause a general-purpose computer, special purpose computer, or special purpose processing device to perform a certain function or group of functions. Computer-executable instructions also include program modules that are executed by computers in stand-alone or network environments. Generally, program modules include routines, programs, components, data structures, objects, and the functions inherent in the design of special-purpose processors, etc. that perform particular tasks or implement particular abstract data types. Computer-executable instructions, associated data structures, and program modules represent examples of the program code means for executing steps of the methods disclosed herein. The particular sequence of executable instructions or associated data structures represents examples of corresponding acts implementing the functions described in the steps.

Those of skill in the art will appreciate that other embodiments of the disclosure may be practiced in network computing environments with many types of system configurations, including personal computers, hand-held devices, multi-processor systems, microprocessor-based or programmable consumer electronics, network PCs, minicomputers, mainframe computers, and the like. Embodiments may also be practiced in distributed computing environments where tasks are performed by local and remote processing devices linked (either by hardwired links, wireless links, or a combination thereof) through a communications network. In a distributed computing environment, program modules can reside in local and/or remote memory storage devices.

The various embodiments described above are provided by way of illustration only and should not be construed to limit the scope of the disclosure. For example, the principles herein are applicable to virtual egifts associated with any type of payment mode, including cash, checks, credit cards, debit cards, loyalty cards, and so forth. The principles herein can be applied to any virtual egift that can be redeemed by using a payment mechanism to make a purchase in the normal fashion without the recipient using a separate physical card or entering a code. Any function disclosed herein in connection with one embodiment can be blended or incorporated into another embodiment. Given generally that redemption of a virtual egift is managed by a policy, any policy features discussed above can be blended to provide new policies, although such new policy is not specifically set forth in a single discussion of any embodiment. Those skilled in the art will readily recognize various modifications and changes that may be made to the principles described herein without following the example embodiments and applications illustrated and described herein, and without departing from the spirit and scope of the disclosure.

Claim language reciting “at least one of” a set indicates that one member of the set or multiple members of the set satisfy the claim. For example, claim language reciting “at least one of A and B” means A, B, or A and B. 

We claim:
 1. A method comprising: receiving, via one or more processors, an identification of a merchant selected by a giver, wherein the giver of a gift credit is associated with a giver payment account, and a recipient of the gift credit is associated with a recipient payment account; associating, via one or more processors, a policy with the gift credit, wherein the policy is at least in part defined by the identification of the merchant; generating an image underlay identifying the gift credit and an image overlay which hides the image underlay and the gift credit identified in the image underlay, the image overlay comprising a separable flap having at least a portion that appears as being unadhered to the image underlay, the separable flap being configured to trigger, in response to an input associated with the separable flap, an animated unwrapping effect that removes the image overlay to reveal the image underlay identifying the gift credit; presenting, via the one or more processors, the image overlay hiding the image underlay; in response to receiving the input associated with the separable flap on the image overlay, generating, via the one or more processors, the animated unwrapping effect to remove the image overlay and reveal the image underlay; and presenting, via the one or more processors, the image underlay and the gift credit.
 2. The method of claim 1, wherein the image underlay identifies the gift credit and the merchant, wherein presenting the image underlay comprises displaying the gift credit and the merchant, and wherein the gift credit corresponds to purchases with the merchant via the recipient payment account.
 3. The method of claim 2, wherein the animated unwrapping effect removes the image overlay to reveal the image underlay identifying the gift credit and the merchant associated with the gift credit.
 4. The method of claim 1, wherein the recipient payment account comprises a credit payment account or a debit payment account.
 5. The method of claim 1, further comprising: monitoring, via one or more processors and according to the policy, purchases using the recipient payment account at a second time, which is later than the first time, to yield purchasing information; based on the purchasing information, determining, via the one or more processors, whether a qualifying purchase has been made at the merchant using the recipient payment account according to the policy; and when the qualifying purchase has occurred, applying, via the one or more processors, at least a portion of the gift credit to the qualifying purchase made at the merchant.
 6. The method of claim 5, further comprising: maintaining an amount of money associated with the gift credit in the giver payment account prior to at least one of the qualifying purchase or the animated unwrapping effect.
 7. The method of claim 6, further comprising: initiating, at a first time prior to the qualifying purchase, a transfer of at least a portion of the amount of money from the giver payment account to a holding account separate from the recipient payment account.
 8. The method of claim 7, further comprising: determining, after transferring the amount of money associated with the gift credit, whether a remaining amount of money exists for the gift credit.
 9. The method of claim 1, wherein the policy further comprises at least one of: a class of goods or services, an amount of money, a ceiling amount of money, a time frame for use of the gift credit, one or more recipient payment accounts that when used can trigger the transfer of at least part of the amount of money from the giver payment account to the one or more recipient payment accounts, and a predetermined period of time in which all the gift credit must be used before the gift credit expires, a remainder amount of money transferrable from the giver payment account to the recipient payment account.
 10. A system comprising: one or more processors; and at least one non-transitory computer readable storage medium having stored thereon instructions which, when executed by the one or more processors, cause the system to: receive an identification of a merchant selected by a giver, wherein the giver of a gift credit is associated with a giver payment account, and a recipient of the gift credit is associated with a recipient payment account; associate a policy with the gift credit, wherein the policy is at least in part defined by the identification of the merchant; generate an image underlay identifying the gift credit and an image overlay which hides the image underlay and the gift credit identified in the image underlay, the image overlay comprising a separable flap having at least a portion that appears as being unadhered to the image underlay, the separable flap being configured to trigger, in response to an input associated with the separable flap, an animated unwrapping effect that removes the image overlay to reveal the image underlay identifying the gift credit; present the image overlay hiding the image underlay; in response to receiving the input associated with the separable flap on the image overlay, generate the animated unwrapping effect to remove the image overlay and reveal the image underlay; and present the image underlay and the gift credit.
 11. The system of claim 10, wherein the image underlay identifies the gift credit and the merchant, wherein presenting the image underlay comprises displaying the gift credit and the merchant, and wherein the gift credit corresponds to purchases with the merchant via the recipient payment account.
 12. The system of claim 11, wherein the animated unwrapping effect removes the image overlay to reveal the image underlay identifying the gift credit and the merchant associated with the gift credit.
 13. The system of claim 10, wherein the recipient payment account comprises a credit or debit payment account.
 14. The system of claim 10, the at least one non-transitory computer readable storage medium having stored thereon instructions which, when executed by the one or more processors, cause the system to: monitor, according to the policy, purchases using the recipient payment account to yield purchasing information; based on the purchasing information, determine whether a qualifying purchase has been made at the merchant using the recipient payment account according to the policy; and when the qualifying purchase has occurred, apply at least a portion of the gift credit to the qualifying purchase made at the merchant.
 15. The system of claim 14, the at least one non-transitory computer readable storage medium having stored thereon instructions which, when executed by the one or more processors, cause the system to: maintain an amount of money associated with the gift credit in the giver payment account prior to at least one of the qualifying purchase or the animated unwrapping effect.
 16. The system of claim 15, the at least one non-transitory computer readable storage medium having stored thereon instructions which, when executed by the one or more processors, cause the system to: initiate, at a first time prior to the qualifying purchase, a transfer of at least a portion of the amount of money from the giver payment account to a holding account separate from the recipient payment account; and determine, after transferring the amount of money associated with the gift credit, whether a remaining amount of money exists for the gift credit.
 17. A method comprising: generating an image underlay identifying a gift credit from a giver and an image overlay which hides the image underlay and the gift credit identified in the image underlay, wherein the giver of the gift credit is associated with a giver payment account, the image overlay comprising a separable flap having at least a portion that appears as being unadhered to the image underlay, the separable flap being configured to trigger, in response to an input associated with the separable flap, an animated unwrapping effect that removes the image overlay to reveal the image underlay identifying the gift credit; and presenting, via the one or more processors, the image overlay hiding the image underlay; in response to receiving the input associated with the separable flap on the image overlay, generating, via the one or more processors, the animated unwrapping effect to remove the image overlay and reveal the image underlay.
 18. The method of claim 17, wherein the image underlay identifies the gift credit and the merchant, the method further comprising presenting the image underlay with an indication of the gift credit and the merchant, and wherein the gift credit corresponds to purchases with the merchant via the recipient payment account.
 19. The method of claim 1, further comprising: monitoring, via one or more processors, purchases using the recipient payment account to yield purchasing information; based on the purchasing information, determining, via the one or more processors, whether a qualifying purchase has been made at the merchant using the recipient payment account according to a policy; and when the qualifying purchase has occurred, applying, via the one or more processors, at least a portion of the gift credit to the qualifying purchase made at the merchant.
 20. The method of claim 19, further comprising: maintaining an amount of money associated with the gift credit in the giver payment account prior to at least one of the qualifying purchase or the animated unwrapping effect; initiating, at a first time prior to the qualifying purchase, a transfer of at least a portion of the amount of money from the giver payment account to a holding account separate from the recipient payment account; and determining, after transferring the amount of money associated with the gift credit, whether a remaining amount of money exists for the gift credit. 